C 01389226

HP StorageWorks XP Command View Advanced Edition software Device Manager user guide
Reference number: T1780-96079 Tenth Edition: February 2008
Legal notices Copyright 2005, 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. ActiveX is a trademark of Microsoft Corp. in the U.S. and other countries. AIX, IBM, and ESCON are registered trademarks of International Business Machines Corporation. BSAFE is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries. Computer Associates is a trademark of Computer Associates International, Inc. in the United States and other countries. Internet Explorer is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. InterSAN is a registered trademark of InterSAN, Inc. in the United States and other countries. Itanium is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Java, Java2, Solaris, Solstice DiskSuite, and Sun are trademarks of Sun Microsystems in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Microsoft is a registered trademark of Microsoft Corp. in the U.S. and other countries. Mozilla is a trademark of the Mozilla Foundation in the U.S and other countries. NetWare is a registered trademark of Novell, Inc. RC2 is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries. RC4 is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries. RSA is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries. Solstice is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries. Solstice DiskSuite is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries. SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc., in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. Sun Fire is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Veritas, and Veritas Storage Foundation are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Windows is a registered trademark of Microsoft Corp. in the U.S. and other countries. Windows Server is a registered trademark of Microsoft Corporation in the United States and/or other countries. Windows Vista is a registered trademark of Microsoft Corporation in the United States and/or other countries. Device Manager includes some parts whose copyrights are reserved by Sun Microsystems, Inc. Device Manager includes some parts whose copyrights are reserved by UNIX System Laboratories, Inc. All other brand or product names are or may be trademarks or service marks of and are used to identify products or services of their respective owners. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP server project. This product includes software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http://www.modssl.org/). This product includes software developed by Greg Stein <gstein@lyra.org> for use in the mod_dav module for Apache (http://www.webdav.org/mod_dav/).
HP StorageWorks XP Command View Advanced Edition software includes RSA BSAFE Cryptographic software from RSA Security Inc. Portions of this software were developed at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign. This product includes software developed by the University of California, Berkeley and its contributors. This software contains code derived from the RSA Data Security Inc. MD5 Message-Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore). This product includes altered versions of software originally developed by Henry Spencer. Part number: T1780-96079 Tenth Edition: February 2008
Contents
Contents
Figures and Tables
Figures ............................................................................................................................................................... 10 Tables................................................................................................................................................................. 12
About this guide

Revision history .................................................................................................................................................. 13 Intended audience.............................................................................................................................................. 17 Prerequisites ...................................................................................................................................................... 18 Document conventions and symbols.................................................................................................................. 18 Conventions: Abbreviations................................................................................................................................ 19 HP technical support .......................................................................................................................................... 20 Subscription service ........................................................................................................................................... 20 HP web sites ...................................................................................................................................................... 21 Documentation feedback.................................................................................................................................... 21
Overview of HP StorageWorks XP Command View Advanced Edition software Device Manager

1-1 Overview ...................................................................................................................................................... 22 1-2 Related software products ........................................................................................................................... 23 1-3 Device Manager components ...................................................................................................................... 24 1-4 Important terms and concepts...................................................................................................................... 25 1-5 Syntax conventions ...................................................................................................................................... 28
Device Manager operations

2-1 User management and access restrictions .................................................................................................. 29 2-1-1 Permissions ......................................................................................................................................... 29 2-1-2 Resource groups ................................................................................................................................. 30 2-1-3 Built-in accounts .................................................................................................................................. 31 2-1-4 Security enhancement at login ............................................................................................................ 31 2-2 Storage management operations................................................................................................................. 32 2-3 Managing storage subsystems .................................................................................................................... 32 2-3-1 Functions supported for each storage subsystem............................................................................... 32 2-3-2 Overview of supported functions ......................................................................................................... 34 2-3-2-1 Assignment and deletion of LUNs .............................................................................................. 34 2-3-2-2 Setting and releasing of LUN security for LUNs ......................................................................... 34 2-3-2-3 Management of logical groups ................................................................................................... 35 2-3-2-4 Configuring LUSE volumes while LUNs are being allocated...................................................... 35 2-3-2-5 Configuring LUSE volumes when using LDEVs for which LUNs are allocated .......................... 35 2-3-2-6 Configuring or releasing LUSE volumes when using LDEVs for which LUNs are not allocated ............................................................................................... 35 2-3-2-7 LUN scanning ............................................................................................................................. 35 2-3-2-8 Detection and removal of storage subsystems........................................................................... 35 2-3-2-9 Acquisition of storage subsystem information ............................................................................ 35 2-3-2-10 Detailed information display and configuration modification of storage subsystems................ 35 2-3-2-11 Creation and deletion of LUNs ................................................................................................. 35 2-3-2-12 Modification of port attributes ................................................................................................... 36 2-3-2-13 Modification of Fibre Channel adapter attributes...................................................................... 36 2-3-2-14 Configuration of command devices and setting of the command device security .................... 36 2-3-2-15 Management of LUN groups and WWN groups ....................................................................... 36 2-3-2-16 Management of host information and host volume information................................................ 36 2-3-2-17 Host refresh function ................................................................................................................ 36 2-3-2-18 Reporting operations ................................................................................................................ 36 2-3-2-19 Alert management .................................................................................................................... 36 2-3-2-20 Viewing and modification of CLPR information ........................................................................ 37
Contents
2-3-2-21 Viewing and modification of SLPR information......................................................................... 37 2-3-2-22 Viewing mainframe volume information.................................................................................... 37 2-3-2-23 Viewing of XP Data Retention Utility information...................................................................... 37 2-3-2-24 Viewing of external volume information.................................................................................... 37 2-3-2-25 Viewing of THP volume information and THP pool information................................................ 37 2-3-2-26 Configuring, changing, or deleting THP volumes and THP pools ............................................ 37 2-3-2-27 XP Business Copy Software..................................................................................................... 37 2-3-2-28 XP Continuous Access Software .............................................................................................. 37 2-3-2-29 XP Snapshot............................................................................................................................. 38 2-3-2-30 XP Continuous Access Journal Software ................................................................................. 38 2-4 Link-and-launch operations.......................................................................................................................... 38 2-5 Report operations......................................................................................................................................... 38 2-6 System security operations .......................................................................................................................... 38 2-7 Linkage with HP SIM.................................................................................................................................... 39
Installing the Device Manager web client

3-1 Requirements for web client operations....................................................................................................... 40 3-2 Preparing to access web client .................................................................................................................... 43 3-3 Installing the Java software environment ..................................................................................................... 44 3-4 Configuring Java software for client/server operations ................................................................................ 45 3-4-1 Setting up the proxy............................................................................................................................. 45 3-4-1-1 For Java Web Start 1.4.2_xx ...................................................................................................... 45 3-4-1-2 For Java Web Start 5.0 and 6.0.................................................................................................. 46 3-4-2 Setting up the log output...................................................................................................................... 47 3-4-3 Setting up Java Web Start................................................................................................................... 48 3-4-3-1 For Java Web Start 1.4.2_xx ...................................................................................................... 48 3-4-3-2 For Java Web Start 5.0 and 6.0.................................................................................................. 48 3-5 Upgrading the Java GUI and clearing the cache ......................................................................................... 49 3-5-1 Upgrading the Java GUI ...................................................................................................................... 49 3-5-2 Clearing the Java Web Start cache ..................................................................................................... 49 3-5-2-1 For JWS 1.4.2_xx ....................................................................................................................... 49 3-5-2-2 For Java Web Start 5.0............................................................................................................... 49 3-5-3 Clearing the browser cache................................................................................................................. 50 3-6 Setting up secure communication with Device Manager ............................................................................. 50
Preparing for and starting operations

4-1 Preparing to start Device Manager operations............................................................................................. 52 4-1-1 Using Device Manager to manage storage subsystems ..................................................................... 52 4-1-2 Tasks required before starting Device Manager operations................................................................ 52 4-2 Link-and-launch Installation requirements ................................................................................................... 53 4-2-1 Application-specific requirements........................................................................................................ 53 4-2-2 Settings for using Mozilla..................................................................................................................... 54 4-2-2-1 Specifying the Mozilla program that you want to use for XP Remote Web Console .................. 54 4-2-2-2 Setting up the Mozilla plug-in. .................................................................................................... 55 4-3 Copy pair requirements................................................................................................................................ 55 4-3-1 P-VOL requirements............................................................................................................................ 55 4-3-2 S-VOL requirements............................................................................................................................ 58 4-3-3 Copy pair volume requirements for RAID levels.................................................................................. 61 4-4 Starting Device Manager operations............................................................................................................ 62 4-5 Linking with XP External Storage Software.................................................................................................. 63 4-5-1 Advantages of linking with the Device Manager.................................................................................. 64 4-5-2 Tasks required for using XP External Storage Software ..................................................................... 64 4-6 Using XP Disk/Cache Partition..................................................................................................................... 65 4-6-1 Cache logical partition function............................................................................................................ 65 4-6-2 Storage logical partition function ......................................................................................................... 65
Performing Device Manager system operations

5-1 Logging in and out of the Device Manager .................................................................................................. 67 5-1-1 Logging in to the Device Manager....................................................................................................... 67 5-1-2 Logging out of Device Manager........................................................................................................... 68
Contents
5-2 Using the Device Manager main window ..................................................................................................... 68 5-2-1 Global tasks bar area .......................................................................................................................... 70 5-2-2 Explorer menu ..................................................................................................................................... 70 5-2-3 Dashboard menu ................................................................................................................................. 71 5-2-4 Application bar area............................................................................................................................. 72 5-2-5 Navigation area ................................................................................................................................... 72 5-2-6 Application area................................................................................................................................... 72 5-2-7 Dialog box............................................................................................................................................ 73 5-2-8 Sortable table ...................................................................................................................................... 73 5-2-8-1 Pagination function ..................................................................................................................... 74 5-2-8-2 Sort function ............................................................................................................................... 74 5-2-8-3 Select all function ....................................................................................................................... 74 5-2-8-4 Selecting a range function .......................................................................................................... 75 5-2-9 Filtering function .................................................................................................................................. 75 5-3 Viewing and installing license information.................................................................................................... 78 5-4 Performing alert operations.......................................................................................................................... 80 5-4-1 Viewing alerts ...................................................................................................................................... 80 5-4-1-1 Viewing all alerts for all storage subsystems.............................................................................. 80 5-4-1-2 Viewing alerts for a selected storage subsystem ....................................................................... 81 5-4-2 Monitoring alerts .................................................................................................................................. 81 5-4-3 Deleting alerts...................................................................................................................................... 82 5-5 Viewing the task list...................................................................................................................................... 82 5-6 Launching other applications from the Device Manager .............................................................................. 83 5-6-1 Launching HDLM................................................................................................................................. 83 5-6-2 Launching XP Provisioning Manager software.................................................................................... 83 5-6-3 Launching XP Tiered Storage Manager software................................................................................ 83 5-6-4 Launching XP Replication Monitor software........................................................................................ 84 5-6-5 Launching XP Remote Web Console (XP1024/XP128) ...................................................................... 84 5-6-6 Launching HP Storage Essentials ....................................................................................................... 84 5-6-7 Launching NAS Manager (XP12000/XP10000/SVS200 and XP1024/XP128).................................... 84 5-6-8 Launching a third-party application...................................................................................................... 85 5-7 Downloading Device Manager software....................................................................................................... 85
Performing user management operations

6-1 Overview of user management operations .................................................................................................. 87 6-2 User management operations...................................................................................................................... 87 6-2-1 Creating a user .................................................................................................................................... 88 6-2-2 Setting permissions for a user ............................................................................................................. 89 6-2-3 Viewing or editing a user profile .......................................................................................................... 90 6-2-3-1 Viewing or editing another user's profile..................................................................................... 90 6-2-3-2 Viewing or editing your own profile ............................................................................................. 91 6-2-4 Changing passwords ........................................................................................................................... 91 6-2-4-1 Changing another user's password ............................................................................................ 91 6-2-4-2 Changing your own password .................................................................................................... 92 6-2-5 Changing the lock status of a user account......................................................................................... 92 6-2-6 Deleting users...................................................................................................................................... 93 6-3 Resource group operations.......................................................................................................................... 93 6-3-1 Creating a resource group................................................................................................................... 93 6-3-2 Assigning a resource group to a user.................................................................................................. 95 6-3-3 Viewing or editing resource group properties ...................................................................................... 97 6-3-4 Deleting a resource group ................................................................................................................... 98 6-4 Setting security options for login .................................................................................................................. 99 6-4-1 Setting password conditions................................................................................................................ 99 6-4-2 Setting automatic locking for user accounts ...................................................................................... 100 6-4-3 Setting a warning banner message ................................................................................................... 101 6-5 Migration from an earlier version................................................................................................................ 103 6-5-1 Migrating user roles ........................................................................................................................... 103 6-5-2 Migrating user groups........................................................................................................................ 104 6-5-3 Migrating user properties................................................................................................................... 104
Performing logical group operations 6
Contents
7-1 Overview of logical groups ......................................................................................................................... 105 7-2 Viewing the list of logical groups ................................................................................................................ 106 7-3 Creating a logical group ............................................................................................................................. 106 7-4 Viewing and editing logical group properties.............................................................................................. 107 7-5 Deleting a logical group.............................................................................................................................. 108 7-6 Storage group operations........................................................................................................................... 109 7-6-1 Viewing the contents of a storage group ........................................................................................... 109 7-6-2 Assigning a path and adding storage to a storage group .................................................................. 115 7-6-3 Moving storage from one group to another ....................................................................................... 127 7-6-4 Modifying LUN security for a group ................................................................................................... 129 7-6-5 Removing storage from a group ........................................................................................................ 132 7-6-6 Deleting a storage group ................................................................................................................... 134
All Storage/My Storage operations

8-1 Overview of All Storage/My Storage operations ........................................................................................ 136 8-2 Viewing the All Storage/My Storage group ................................................................................................ 136 8-2-1 Viewing the Open-Allocated group for a subsystem.......................................................................... 137 8-2-2 Viewing the Open-Unallocated group for a subsystem ..................................................................... 143 8-2-3 Viewing the Open-Reserved group for a subsystem ......................................................................... 147 8-2-4 Viewing the Mainframe-Unspecified group........................................................................................ 151 8-2-5 Viewing the Pools group.................................................................................................................... 153 8-3 Performing a LUN Scan operation ............................................................................................................. 154 8-4 Allocating storage....................................................................................................................................... 155 8-5 Unallocating storage .................................................................................................................................. 155 8-6 Creating LUSE volumes............................................................................................................................. 158 8-6-1 Requirements of LDEVs that constitute a LUSE volume................................................................... 158 8-6-2 Creating a LUSE volume with LDEVs with allocated paths............................................................... 159 8-6-3 Creating a LUSE volume with LDEVs with no allocated path............................................................ 160 8-7 Deleting LUSE volumes ............................................................................................................................. 162 8-8 Managing XP Thin Provisioning Software pools ........................................................................................ 162 8-8-1 Viewing XP Thin Provisioning Software pools................................................................................... 163 8-8-2 Managing THP pools ......................................................................................................................... 163 8-8-2-1 Creating a THP pool ................................................................................................................. 164 8-8-2-2 Changing the THP pool threshold value................................................................................... 166 8-8-2-3 Expanding the capacity of a THP pool ..................................................................................... 167 8-8-2-4 Deleting THP pools................................................................................................................... 168 8-8-3 Managing THP volumes .................................................................................................................... 168 8-8-3-1 Creating THP volumes ............................................................................................................. 168 8-8-3-2 Changing a THP volume threshold value ................................................................................. 171 8-8-3-3 Deleting THP volumes.............................................................................................................. 172 8-8-4 Viewing information about THP volumes not assigned to THP pools ............................................... 173
Performing host operations

9-1 Overview of Device Manager host operations ........................................................................................... 174 9-2 Information that can be acquired from the Device Manager agent ............................................................ 175 9-2-1 When a host has a single path configuration..................................................................................... 176 9-2-2 When a host has a multi-path configuration ...................................................................................... 176 9-2-3 When a host has no path assigned ................................................................................................... 176 9-3 Viewing the list of hosts.............................................................................................................................. 177 9-4 Adding a host ............................................................................................................................................. 177 9-4-1 Adding hosts by using the Device Manager agent ............................................................................ 178 9-4-2 Adding hosts manually ...................................................................................................................... 178 9-5 Viewing host properties and storage information ....................................................................................... 180 9-6 Modifying host properties ........................................................................................................................... 182 9-7 Adding storage from host management ..................................................................................................... 185 9-8 Updating (refreshing) host information....................................................................................................... 185 9-9 Managing copy pairs .................................................................................................................................. 186 9-9-1 Creating copy pairs............................................................................................................................ 187 9-9-2 Modifying copy pairs.......................................................................................................................... 193
Contents
9-9-3 Notes on copy pair operations........................................................................................................... 196 9-9-4 Deleting copy pairs ............................................................................................................................ 201 9-10 Removing a host ...................................................................................................................................... 202 9-10-1 Removing multiple hosts in one operation....................................................................................... 203 9-10-2 Removing hosts one by one ............................................................................................................ 203 9-11 Applying WWN information when replacing host bus adapters ............................................................... 203
10 Performing storage subsystem operations

10-1 Overview of storage subsystem operations ............................................................................................. 205 10-1-1 Viewing a list of storage subsystems............................................................................................... 206 10-1-2 Adding a storage subsystem ........................................................................................................... 206 10-1-3 Viewing and editing storage subsystem properties ......................................................................... 208 10-1-4 Performing a refresh operation........................................................................................................ 210 10-1-5 Adding a new IP address................................................................................................................. 210 10-1-6 Removing a storage subsystem ...................................................................................................... 211 10-2 Viewing detailed information and changing configuration of the storage subsystem............................... 211 10-2-1 Viewing information for XP24000/XP20000 .................................................................................... 212 10-2-2 Viewing information for XP12000/XP10000/SVS200 ...................................................................... 212 10-2-3 Viewing information for XP1024/XP128 .......................................................................................... 213 10-2-4 Viewing information for XP512/XP48 .............................................................................................. 220 10-2-5 Viewing LDEV information............................................................................................................... 224 10-3 Port operations......................................................................................................................................... 228 10-3-1 Configuring ports (XP1024/XP128 and XP512/XP48)..................................................................... 229 10-3-2 Managing LUN groups..................................................................................................................... 231 10-3-2-1 Creating a LUN group............................................................................................................. 233 10-3-2-2 Modifying a LUN group........................................................................................................... 234 10-3-2-3 Deleting a LUN group ............................................................................................................. 235 10-3-3 Managing WWN groups .................................................................................................................. 235 10-3-3-1 Creating a WWN group .......................................................................................................... 236 10-3-3-2 Modifying a WWN group......................................................................................................... 237 10-3-3-3 Deleting a WWN group........................................................................................................... 237 10-3-4 Configuring Fibre Channel adapters (XP1024/XP128 and XP512/XP48) ....................................... 238 10-4 LDEV operations ...................................................................................................................................... 239 10-4-1 Allocating storage (adding volume paths) ....................................................................................... 240 10-4-2 Unallocating storage (removing volume paths) ............................................................................... 243 10-4-3 Creating an LDEV............................................................................................................................ 244 10-4-4 Deleting an LDEV ............................................................................................................................ 246 10-4-5 Setting or canceling a command device.......................................................................................... 247
11 Performing report operations

11-1 Overview of Device Manager reports....................................................................................................... 249 11-2 Physical configuration of the storage subsystem report........................................................................... 250 11-3 Storage utilization by host report.............................................................................................................. 250 11-4 Storage utilization by logical group report ................................................................................................ 250 11-5 Users and resource groups report ........................................................................................................... 251 11-6 LDEV details report .................................................................................................................................. 251
12 Troubleshooting
12-1 Troubleshooting operations...................................................................................................................... 254 12-2 Countermeasures..................................................................................................................................... 254 12-3 Warning messages .................................................................................................................................. 260 12-3-1 User data might be deleted ............................................................................................................. 260 12-3-2 An error occurs in I/O from hosts..................................................................................................... 260 12-3-3 LUN security automatically takes effect........................................................................................... 261 12-3-4 Access from hosts is disabled ......................................................................................................... 261 12-3-5 Data in an S-VOL (secondary volume) is incomplete...................................................................... 261 12-3-6 Pair setting cannot be performed .................................................................................................... 261 12-3-7 An internal volume to which an external volume is mapped is invalid............................................. 262 12-3-8 Creating LUSE volumes from multiple external subsystems........................................................... 262 12-3-9 Associating resources with different SLPRs.................................................................................... 262 12-3-10 Associating resources with different CLPRs.................................................................................. 262
Contents
12-3-11 Displaying a window while updating the storage subsystem......................................................... 263 12-3-12 Running a LUN Scan..................................................................................................................... 263 12-4 Error messages........................................................................................................................................ 263
Glossary Index
Figures and Tables
Figures and Tables

Figures
Figure 1-1 XP Command View AE software Device Manager system components ................................................. 25 Figure 2-1 Example of a warning banner message .................................................................................................. 32 Figure 4-1 System configuration using XP External Storage Software ..................................................................... 63 Figure 4-2 Using the storage logical partition function .............................................................................................. 66 Figure 5-1 Device Manager main window components ............................................................................................ 69 Figure 5-2 Sortable table........................................................................................................................................... 73 Figure 5-3 Filter dialog box ....................................................................................................................................... 75 Figure 5-4 Device Manager License Information dialog box ..................................................................................... 79 Figure 5-5 List ObjectsAlerts subwindow ................................................................................................................ 80 Figure 6-1 User-ID subwindow ................................................................................................................................... 89 Figure 6-2 Change Permissionuser-ID dialog box.................................................................................................... 90 Figure 6-3 Resource Group Administration dialog box ............................................................................................. 94 Figure 6-4 Creating a resource group ....................................................................................................................... 94 Figure 6-5 Resource Group Allocation dialog box .................................................................................................... 96 Figure 6-6 Change Resource Group dialog box ....................................................................................................... 97 Figure 6-7 Changing resource group properties ....................................................................................................... 98 Figure 6-8 Setting password conditions .................................................................................................................. 100 Figure 6-9 Setting automatic account locking ......................................................................................................... 101 Figure 6-10 Warning banner message edited correctly .......................................................................................... 103 Figure 7-1 Creating a logical group......................................................................................................................... 107 Figure 7-2 Modifying properties .............................................................................................................................. 108 Figure 7-3 Viewing the contents of a storage group ............................................................................................... 110 Figure 7-4 Adding storageselecting the storage addition operation ...................................................................... 117 Figure 7-5 Adding storageselecting ports ............................................................................................................. 118 Figure 7-6 Adding storagedefining host/port connections ..................................................................................... 119 Figure 7-7 Host Storage Domain Info ..................................................................................................................... 121 Figure 7-8 Adding storageallocating storage ........................................................................................................ 121 Figure 7-9 Adding storagebrowsing for LDEVs ..................................................................................................... 122 Figure 7-10 Adding storagestorage found............................................................................................................. 123 Figure 7-11 Adding storagedefining LUs............................................................................................................... 124 Figure 7-12 Adding storageassigning host/port connection .................................................................................. 125 Figure 7-13 Adding storageassigning LUNs ......................................................................................................... 126 Figure 7-14 Adding storageconfirmation ............................................................................................................... 127 Figure 7-15 Moving storageselecting the path(s).................................................................................................. 128 Figure 7-16 Moving storageselecting the target storage group............................................................................. 129 Figure 7-17 Modifying securityStep 1: Select Hosts ............................................................................................. 130 Figure 7-18 Modifying securityStep 2: Select WWNs ........................................................................................... 131 Figure 7-19 Modifying securitywarning ................................................................................................................. 131 Figure 7-20 Removing storage groupsconfirmation .............................................................................................. 133 Figure 7-21 Deleting a logical groupconfirmation.................................................................................................. 134 Figure 8-1 Selecting the path(s) window ................................................................................................................. 156 Figure 8-2 Unallocating storageconfirmation window ........................................................................................... 157 Figure 8-3 Unallocating storage LUSEconfirmation window ................................................................................. 157 Figure 8-4 Creating LUSEselecting LDEVs .......................................................................................................... 161
10
Figures and Tables

Figure 8-5 Create THP Pool (Step 2: Create THP Pool) dialog box ....................................................................... 165 Figure 8-6 Create THP Pool (Step 3: Select THP Pool VOLs) dialog box .............................................................. 166 Figure 8-7 Modify THP Pool dialog box .................................................................................................................. 167 Figure 8-8 Create THP VOLs (Step 2: Create THP VOLs) dialog box.................................................................... 169 Figure 8-9 Create THP VOLs (Step 3: Edit THP VOLs) dialog box ........................................................................ 170 Figure 8-10 Edit THP VOL dialog box..................................................................................................................... 170 Figure 8-11 Modify THP VOL dialog box ................................................................................................................ 172 Figure 9-1 Hosts object ........................................................................................................................................... 175 Figure 9-2 Adding a hostentering the name.......................................................................................................... 178 Figure 9-3 Add HostSelect WWNs ........................................................................................................................ 180 Figure 9-4 Modifying host properties....................................................................................................................... 182 Figure 9-5 Modifying host propertiesselecting LUN security changes .................................................................. 184 Figure 9-6 Creating a pairchoosing pair(s) step .................................................................................................... 188 Figure 9-7 Creating a pairselecting S-VOL(s) ....................................................................................................... 189 Figure 9-8 Creating a pairdefining pair(s) step...................................................................................................... 190 Figure 9-9 Creating a pairviewing pair information ............................................................................................... 190 Figure 9-10 Creating a pairdefining a new copy group ......................................................................................... 192 Figure 9-11 Selecting a journal group ..................................................................................................................... 192 Figure 9-12 Creating a pairconfirmation step ........................................................................................................ 193 Figure 9-13 Modifying a pairselect modify pair(s) step ......................................................................................... 195 Figure 9-14 Modifying pair(s) step .......................................................................................................................... 196 Figure 9-15 Deleting a pairselect delete pair(s) step ............................................................................................ 202 Figure 10-1 Modifying properties ............................................................................................................................ 209 Figure 10-2 Physical View for XP1024/XP128 (Configuration) ............................................................................... 214 Figure 10-3 Physical View for XP1024/XP128 (Array Groups) ............................................................................... 215 Figure 10-4 Frame Information window for XP1024/XP128 (Level 1) .................................................................... 216 Figure 10-5 Discrete VDEV configuration for XP1024/XP128 ................................................................................ 217 Figure 10-6 Frame Information window for discrete VDEV configuration ............................................................... 218 Figure 10-7 Frame Information window for XP1024/XP128 (Level 2)..................................................................... 219 Figure 10-8 Physical View for XP1024/XP128 (Disks)............................................................................................ 220 Figure 10-9 Physical View for XP512/XP48 (Configuration) ................................................................................... 221 Figure 10-10 Physical View for XP512/XP48 (Array Groups) ................................................................................. 222 Figure 10-11 Frame Information window for XP512/XP48...................................................................................... 223 Figure 10-12 Physical View for XP512/XP48 (Disks).............................................................................................. 224 Figure 10-13 Port Information window for the XP1024/XP128 ............................................................................... 230 Figure 10-14 Modify LUN Group window ................................................................................................................ 232 Figure 10-15 Creating a new LUN GroupSelecting the WWN(s) .......................................................................... 233 Figure 10-16 Creating a new LUN GroupSelecting the WWN Group(s) ............................................................... 234 Figure 10-17 Modify WWN Group window.............................................................................................................. 236 Figure 10-18 Changing the channel adapter mode (XP1024/XP128)..................................................................... 239 Figure 10-19 Allocating storagedefining host/port connections ............................................................................ 241 Figure 10-20 Allocating storageassigning host/port connections .......................................................................... 241 Figure 10-21 Allocating storageassigning LUNs ................................................................................................... 242 Figure 10-22 Allocating storageconfirmation......................................................................................................... 243 Figure 10-23 Creating an LDEVspecifying LDEV parameters (XP512/XP48) ...................................................... 246 Figure 11-1 Reports subwindow (A list of detailed array reports) ........................................................................... 251 Figure 11-2 Create Detailed Array ReportReport dialog box ................................................................................ 252
11
Figures and Tables
Tables
Table 1 Revisions ..................................................................................................................................................... 13 Table 2 Document conventions ................................................................................................................................ 18 Table 3 Conventions: Abbreviations ......................................................................................................................... 19 Table 1-1 Device Manager and corresponding storage subsystem terms ............................................................... 28 Table 1-2 Syntax conventions .................................................................................................................................. 28 Table 2-1 List of permissions.................................................................................................................................... 30 Table 2-2 Functions for each storage subsystem that are supported by web client................................................. 33 Table 4-1 Common requirements for a logical device to be selectable as a primary volume (SP-VOL).................. 56 Table 4-2 Requirements for a logical device to be selectable as a primary volume (SP-VOL) for XP24000/XP20000 ................................................................................................................................................................................... 56 Table 4-3 Requirements for a logical device to be selectable as a primary volume (SP-VOL) for XP12000/XP10000/SVS200 ...................................................................................................................................... 57 Table 4-4 Requirements for a logical device to be selectable as a primary volume (SP-VOL) for XP1024/XP128 and XP512/XP48 ....................................................................................................................................................... 58 Table 4-5 Common requirements for a logical device to be selectable as a secondary volume .............................. 59 Table 4-6 Requirements for a logical device to be selectable as a secondary volume for XP24000/XP20000 ....... 59 Table 4-7 Requirements for a logical device to be selectable as a secondary volume for XP12000/XP10000/SVS200 ...................................................................................................................................... 60 Table 4-8 Requirements for a logical device to be selectable as a secondary volume for XP1024/XP128 and XP512/XP48 .............................................................................................................................................................. 61 Table 4-9 Combinations of RAID levels for copy pair volumes ................................................................................ 61 Table 5-1 Product names and corresponding dashboard menu items ..................................................................... 72 Table 5-2 Filtering conditions ................................................................................................................................... 76 Table 5-3 Alert severity codes .................................................................................................................................. 81 Table 6-1 Migration of user roles ............................................................................................................................ 104 Table 6-2 Migration of user properties .................................................................................................................... 104 Table 7-1 LDEV-number window detailed information.............................................................................................. 111 Table 8-1 Open-Allocated group information under All Storage/My Storage ......................................................... 138 Table 8-2 Open-Unallocated group information under All Storage/My Storage ..................................................... 143 Table 8-3 Information for the Open-Reserved group under All Storage/My Storage ............................................. 148 Table 8-4 Information for the Mainframe-Unspecified group under All Storage/My Storage.................................. 151 Table 8-5 Requirements of LDEVs that make up a LUSE volume ......................................................................... 158 Table 9-1 Information displayed in a multi-path configuration ................................................................................. 176 Table 9-2 Information displayed when a host has no path assigned...................................................................... 177 Table 9-3 Requirements for modify pair operations ............................................................................................... 194 Table 9-4 Modifying XP Business Copy Software cascade pairs ........................................................................... 194 Table 9-5 Items to consider before creating copy pairs.......................................................................................... 197 Table 9-6 Notes on copy pair operations................................................................................................................ 197 Table 9-7 Notes on managing the host .................................................................................................................. 200 Table 10-1 Available AL-PA values ........................................................................................................................ 229 Table 10-2 Maximum capacities of standard LU types........................................................................................... 244 Table 12-1 General troubleshooting information .................................................................................................... 254
12
About this guide
About this guide

This document describes and provides instructions for using the HP StorageWorks XP Advanced Edition software Device Manager web client (subsequently called the web client) to manage storage on HP StorageWorks XP disk arrays storage virtualization systems.
Revision history
Table 1 Revisions Date
July 2005 October 2005
Edition Revision
First Second Initial Release
The character string displayed for the copy type has been changed. Linkage to XP Provisioning Manager, XP Replication Monitor, and XP Tiered
Storage Manager is now supported.
A link to the online manual site of Hewlett Packard has been added. Warning messages have been changed.
February 2006 Third
The new GUI is now supported. New User Account Management is now supported. A sortable table is used to list objects in the information area or a dialog box.
Functionality to link with mainframe agent has been added. The VOLSER and DEVN of a mainframe volume can now be referenced. Mozilla 1.7.12.01 provided by HP is now supported. Multiple hosts can now be deleted at the same time. The user can now choose whether to change LUN security when deleting a host or modifying host properties. have already been set for LUN security.
May 2006
Fourth
The user can now select the WWN for a host from a list of unused WWNs that To enhance security at login, the following functions are now supported:
Locking a user account when the number of login attempts reaches a specified count Locking and unlocking of user accounts Displaying a warning message in the Login window Setting conditions for passwords
A new function is now supported, by which the user can add a storage that
has the same ports and LUN security as the storage for which paths are set.
The date and time for the last time a storage subsystem was refreshed, or the
time a storage subsystem was added, can now be displayed.
The following LDEV attributes can now be displayed:

On-demand volume Reserve volume for use in XP Auto LUN Software The POOL ID of a data pool
13
About this guide
Table 1 Revisions Date Edition Revision In Device Manager web client, the user can now set password conditions,
automatic account locking, and warning banner messages as security options.
November 2006 Fifth
Windows Server 2003 R2 is now supported as a new OS. Sun Solaris 10 is now supported as a new OS. JRE version 5.0 is now supported. The user can now determine whether the area that contains the Explorer menu and Dashboard menu is shown or hidden. display per page.
The user can now select the number of lines that the sortable table can New objects for the filter function have been added. The user can now use a greater number of characters when setting a user ID
or password.
The method for selecting a parent group when creating a logical group has
been changed.
Device Manager web client now displays only the WWNs of previously
selected hosts when adding storage from host management.
The display order of the items in a sortable table has been changed. Action to be taken if the Java GUI cannot be started when web client is
connected to a Device Manager server by using SSL has been added.
A character string that represents a remote command device can now be

displayed in the LDEV attribute.
FATA can now be displayed in the Type attribute of an LDEV. Information for troubleshooting has been added. A warning message issued when a copy pair cannot be created has been
added.
14
About this guide

February 2007
Edition Revision
Sixth
XP Continuous Access Journal Software copy pairs can now be created,

changed, and deleted.
Copy pair volume has been added to Important Terms and Concepts. Linkage with HP SIM (HP Systems Insight Manager) is now supported. The Mozilla 1.7 browsers is now supported on Solaris 9. The description of the Java environment setup method has been changed. A description of the Java environment setup method in JWS version 5.0 has been added.
Regular hosts and external ports can now be displayed separately. The explanation of items that can be specified for filtering conditions has been
changed to a table format.
Filter function object items have been added. The status of an LDEV can now be displayed in the Detailed Information
LDEV-number dialog box.
The item name JNL Group has been changed to Journal Group. The maximum byte number displayed in File System is now described. A description has been added for when n/a is displayed for a display item. When storage is added, any number of LUNs can now be assigned as the start number in ascending order. The WWN nickname can now be displayed. The explanation of % Used has been improved. The explanation of FATA has been deleted. If the host selected in the navigation area centrally manages copy pairs, information of centrally managed copy pairs is now displayed. If the selected host does not centrally manage copy pairs, information of copy pairs managed by this host is now displayed. enclosed in double quotation marks.
A CSV format report can now be output in a format in which each value is
15
About this guide

June 2007
Edition Revision
Seventh
XP24000 is now supported as a new storage subsystem. The XP Thin Provisioning Software of XP24000 is now supported. Detailed Array Reports that output LDEV detailed information in CSV format
have been added.
Windows Server 2003 SP 2 is now supported as an applicable OS. Windows Server 2003 R2 SP 2 is now supported as an applicable OS. Windows Vista is now supported as an applicable OS. HP-UX 11i v3 is now supported as an applicable OS. Mozilla 1.7.13.01 is now supported as an applicable web browser available in HP-UX 11i v3.
JRE version 6.0 is now supported. Internet Explorer 7.0 is now supported as an applicable web browser. The Open-Reserved group, which displays the open volumes that cannot be
assigned a path, has been added to All Storage (My Storage). The OpenUnallocated group now displays only the open volumes that can be assigned a path.
Device Manager web client can now display the actual amount of LDEV space
in a storage subsystem.
The number of LDEVs, LUNs, and LUSE volumes that can be manipulated by
one operation has been limited.
The preparation procedure for Device Manager operations has been changed. The description of XP Disk/Cache Partition has been moved to Chapter 4. A note on the Java heap size that must be set when using XP Remote Web
Console has been added.
Information for troubleshooting has been added.

September 2007 Eighth
The Solaris 10 (x64 edition) operating system is now supported. Array groups can now be filtered by specifying a partial match in the filtering
conditions.
The Core CLI/SMI-S license for Device Manager is now supported. A Back button for re-executing a process is now supported in error windows. The XP20000 storage subsystem is now supported. Functions supported for each storage subsystem are now listed in a table. Descriptions related to LUN Scan operations have been revised. Accordingly, the description in 9-4-1 has been changed to the method to add a host by using the Device Manager agent.
MF-JNL has been added as a volume attribute. Screenshots have been revised, and some screenshots have been deleted.
16
About this guide

January 2008
Edition Revision
Ninth
The following THP functions are now supported for XP24000/XP20000:

THP volumes and pools can now be created in storage subsystems. Information about THP pools can now be displayed in the Detailed Information-LDEV-number dialog box. Pool IDs can now be displayed as LDEV information.
In XP24000/XP20000, XP12000/XP10000/SVS200, and XP1024/XP128, it is

now possible to create LUSE volumes with a path-allocated LDEV.
The methods that were displayed in the summary area of the main window are
now changed to buttons. As a result, the area combining the summary area and information area has been expanded as the application area.
The following filtering function has been expanded:

An LDEV range can now be specified as a single condition value. When multiple conditions are set, the OR condition can now be used for filtering.
In XP24000/XP20000, functionality to identify SATA drives has been added.

As a result, volumes that contain SATA drives can now be identified and displayed.
In the Detailed Information-LDEV-number dialog box, the number of blocks

can now be displayed.
The character string displayed as the volume attribute that indicates a THP
pool volume has been changed to THP-Pool-VOL.
You can now use Internet Explorer 7.0 in Windows Server 2003 R2. Linux is now supported as a new OS. You can now use IP addresses in the IPv6 format. A path that belongs to a different storage group now can be selected when using the Add Like Storage feature. The support status of the management tools for each OS has been changed. Windows 2000 Service Pack 3 is no longer supported. Item that need to be checked when using Internet Explorer have been added. An explanation of how to configure a firewall has been added. The procedure for defining the connection between a host and a port when adding storage has been improved.
The system disk of XP24000/XP20000 can now be displayed. The characters you can enter for Name have been changed.
February 2008 Tenth
In XP24000/XP20000 and XP12000/XP10000/SVS200, the LDEV

requirement has been changed for selecting a copy pair volume of XP Snapshot as a P-VOL for XP Continuous Access Software.
In XP24000/XP20000 of microcode version 60-02-4x-xx/xx or later, it is now

possible to use THP volumes for XP Continuous Access Software and XP Continuous Access Journal Software.
In the requirements for an LDEV that can be used as a THP pool volume, the
upper limit of the LDEV capacity has been changed.
Intended audience
This document is intended for customers and HP-authorized service personnel who:
Have a background in data processing and understand peripheral storage devices and their basic functions. 17
About this guide
Are familiar with the operating system that hosts the web client.
Prerequisites
Prerequisites for installing this product include:
Reading through the user guide Meeting all the minimum installation requirements Reviewing the release notes on the CD for any last-minute announcements
Document conventions and symbols

Table 2 Document conventions Convention Element
Medium blue text: Figure 1 Medium blue, underlined text (http://www.hp.com) Bold font
Convention Element
Cross-reference links and e-mail addresses Web site addresses
Key names Text typed into a GUI element, such as into a box GUI elements that are to be clicked or selected, such as menu and list
items, buttons, tabs, and check boxes Text emphasis
italics font Monospace font
File and directory names System output Code Text typed at the command-line
Monospace, italic font
Code variables Command-line variables

Emphasis of file and directory names, system output, code, and text typed at the command-line
Monospace, bold font
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.
18
About this guide
Conventions: Abbreviations
This manual uses the following abbreviations for product names. Table 3 Conventions: Abbreviations Abbreviation
XP Auto LUN Software
Full name or meaning

This abbreviation is used when it is not necessary to distinguish the following products:
XP Auto LUN Software Auto LUN XP (Volume Migration)

XP Business Copy Software This abbreviation is used when it is not necessary to distinguish the following products:
XP Business Copy Software Business Copy XP

XP Cache Residency Manager This abbreviation is used when it is not necessary to distinguish the following products:
XP Cache Residency Manager Cache LUN XP

XP Continuous Access Asynchronous Software This abbreviation is used when it is not necessary to distinguish the following products:
XP Continuous Access Asynchronous Software Continuous Access XP Asynchronous Continuous Access XP Extension
XP Continuous Access Journal Software This abbreviation is used when it is not necessary to distinguish the following products:
XP Continuous Access Journal Software Continuous Access XP Journal

XP Continuous Access Software This abbreviation is used when it is not necessary to distinguish the following products:
XP Continuous Access Synchronous Software Continuous Access XP

XP Continuous Access Synchronous Software This abbreviation is used when it is not necessary to distinguish the following products:
XP Continuous Access Synchronous Software Continuous Access XP Synchronous

XP Data Retention Utility This abbreviation is used when it is not necessary to distinguish the following products:
XP Data Retention Utility LUN Security XP Extension

XP External Storage Software This abbreviation is used when it is not necessary to distinguish the following products:
XP External Storage Software External Storage XP

XP Flex Copy This abbreviation is used when it is not necessary to distinguish the following products:
XP Flex Copy Flex Copy XP
19
About this guide
Table 3 Conventions: Abbreviations Abbreviation

XP LUN Expansion
Full name or meaning

This abbreviation is used when it is not necessary to distinguish the following products:
XP LUN Expansion LUN Configuration and Security Manager XP (LUN Expansion)

XP LUN Manager This abbreviation is used when it is not necessary to distinguish the following products:
XP LUN Manager LUN Management

XP RAID Manager This abbreviation is used when it is not necessary to distinguish the following products:
XP RAID Manager RAID Manager XP

XP Snapshot This abbreviation is used when it is not necessary to distinguish the following products:
XP Snapshot Snapshot XP
XP Virtual LVI/LUN (VLL) and Volume Shredder This abbreviation is used when it is not necessary to distinguish the following products:
XP Virtual LVI/LUN (VLL) and Volume Shredder Security Manager XP XP Data Shredder LUN Configuration and Security Manager XP (Virtual LVI) Open Volume Management
HP technical support
Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support. Collect the following information before calling:
Technical support registration number (if applicable) Product serial numbers Product model names and numbers Error messages Operating system type and revision level Detailed questions
For continuous quality improvement, calls may be recorded or monitored.
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business web site: http://www.hp.com/go/e-updates. After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources.
20
About this guide
HP web sites
For additional information, see the following HP web sites:
http://www.hp.com/ http://www.hp.com/go/storage http://www.hp.com/service_locator http://www.docs.hp.com
Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to storagedocsFeedback@hp.com. All submissions become the property of HP.
21

This chapter provides an overview of HP StorageWorks XP Command View Advanced Edition software Device Manager (subsequently called the Device Manager):
Overview (see section 1-1 ) Related software products (see section 1-2 ) Device Manager components (see section 1-3 ) Important terms and concepts (see section 1-4 ) Syntax conventions (see section 1-5 )
1-1 Overview
HP StorageWorks XP Command View Advanced Edition software Device Manager (called the Device Manager in this guide) is another name for HP StorageWorks XP Command View Advanced Edition software. The Device Manager is storage management software that allows users to consolidate storage operations and manage capacity in multiple storage subsystems (also called subsystems and disk arrays). Supported storage subsystems include, HP StorageWorks XP disk array models, HP XP24000, HP XP20000, HP XP12000, HP XP10000, XP1024, XP128, XP512, and XP48, and the HP StorageWorks 200 Storage Virtualization System (HP SVS200). The HP StorageWorks XP256 Disk Array is not supported. The Device Manager discovers the configuration attributes of storage subsystems in open or shared environments and allows you to manage complex and heterogeneous storage using an easy-to-use, browser-based GUI. You can perform operations such as adding or removing storage, configuring volume paths and Fibre Channel ports, creating custom-size volumes, managing LUN security, and managing copy pairs. The Device Manager also provides link-and-launch integration with XP Command View AE Suite (a collective name for HP StorageWorks XP Command View Advanced Edition software and plug-in products) and management tools used exclusively for storage subsystems. The Device Manager system includes the Device Manager server, the storage subsystem(s) connected to the server, optional Device Manager agents, and the Device Manager web and CLI clients. The Device Manager web client provides a browser-based GUI for real-time interaction with managed storage subsystems. The Device Manager command line interface (CLI) is for users who want to create scripts for automation. Designed as an open framework, the Device Manager provides application programming interfaces (APIs) that allow other applications such as HP Systems Insight Manager and HP Storage Essentials to integrate with the Device Manager. These APIs also enable industry-leading software vendors, such as Symantec, Microsoft, BMC, Computer Associates, Sun Microsystems, and InterSAN, to integrate their applications with the Device Manager. You can also "plug in" existing or new applications to the Device Manager system. Additional features of the Device Manager include:
User-defined hierarchical management groups Detailed views of storage subsystem configuration
22
Alerts Ability to monitor and display logical volume usage statistics using the Device Manager agent Built-in report facility including preformatted (HTML) reports and comma-separated values for export Access control: Access control using permissions (Admin, Modify, and View) and resource groups Storage management: Storage configuration and manipulation System support: web client support, user administration, agent activity, and security
The Device Manager controls access and functionality for levels of users:
1-2 Related software products

The following software products are related to the Device Manager:
Hitachi Dynamic Link Manager (HDLM) manages access paths to and from the hosts where it is installed. For example, HDLM allows you to set up automatic failover, failback, and load balancing.The HDLM GUI can be viewed from the Device Manager web client (see section 2-4 ). For details on HDLM, refer to the HDLM manuals. XP Provisioning Manager software automates the operations for allocating LDEVs to the server and expanding file systems. This XP Command View AE Suite software plug-in selects appropriate storage, creates device files on the server, and creates and mounts file systems. The XP Provisioning Manager software GUI can be viewed from the web client (see section 24 ). For details about XP Provisioning Manager software, see the XP Provisioning Manager software manuals. XP Tiered Storage Manager software provides a means to move data to the best-suited storage subsystem based on the characteristics of the data (severity level or access frequency). You can optimize the allocation of data in an environment containing integrated storage subsystems with XP24000/XP20000 or XP12000/XP10000/SVS200 as the core storage subsystems. The XP Tiered Storage Manager software GUI can be displayed from web client (see section 2-4 ). For details about XP Tiered Storage Manager software, see the XP Tiered Storage Manager software documentation. XP Replication Monitor software displays the configuration of copy pairs in the entire system from the aspects of the configuration definitions of hosts, storage subsystems, and copy pairs, so you can easily understand the configuration of copy pairs. By specifying monitoring settings, you can automatically notify users if an error occurs. The XP Replication Monitor software GUI can be viewed from web client (see section 2-4 ). For details on XP Replication Monitor software, see the XP Replication Monitor software manuals. The HP StorageWorks XP Command View Advanced Edition software mainframe agent provides information of volumes used by a mainframe host. This allows volume information that previously could only be monitored on the mainframe host system to be monitored from a Device Manager client program, thereby facilitating centralized management of distributed resources. For details on mainframe agent, see the HP StorageWorks XP Command View Advanced Edition software mainframe agent documentation. For information on setting the environment to link with mainframe agent, see the HP StorageWorks XP Command View Advanced Edition software Device Manager CLI user guide. HP Storage Essentials acts as the main console for heterogeneous storage infrastructure management software, providing SAN visualization and reporting, asset management, performance and capacity monitoring and planning, and policy-driven event management. The Storage Essentials GUI can be viewed from web client (see section 2-4 ). For details about Storage Essentials, see the Storage Essentials documentation. HP Systems Insight Manager combines the strengths of Insight Manager 7, HP Toptools, and HP Servicecontrol Manager to deliver a single tool for managing HP ProLiant, Integrity, and HP 23
Overview of HP StorageWorks XP Command View Advanced Edition software Device Manager 9000 systems running Microsoft Windows, Linux, HP-UX, Open VMS, and NonStop. The core software uses WBEM to deliver the essential capabilities required to manage all HP server platforms.
1-3 Device Manager components

The Device Manager system comprises the following software components (see Figure 1-1):
Device Manager supports integration with the XP Command View AE Common Component, which provides features that are common to all XP Command View AE Suite software. The provided features are Single Sign-On user authentication and integrated logging. Each XP Command View AE Suite software now includes XP Command View AE Common Component.
Single Sign-On. Integrated Single Sign-On is used for link-and-launch operations (see
section 2-4 ). The already authenticated user ID and password are available to the launched products so that the user does not need to re-enter a user ID and password. User permissions can be set for each XP Command View AE Suite. For details about link-and-launch operations, see section 5-6 .
Common logging. The integrated logging feature provides a common log repository for
the various logs of the XP Command View AE Suite software.
The Device Manager server is attached via a LAN to the storage subsystems. The server controls Device Manager operations based on requests from Device Manager clients (for example, web client, CLI, and third-party applications).
NOTE: For further information on the Device Manager server, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide.
Clients:
The Device Manager web client provides two types of user interfaces, an HTML GUI
and a Java GUI, for Device Manager functions. The web client communicates with and runs as a client of the Device Manager server. The HTML GUI is a browser-based application that can be accessed from web browsers. This GUI provides the windows and dialog boxes for features other than the storage subsystem and resource group management features. The Java GUI is a Java-based application. This GUI provides the windows and dialog boxes for the storage subsystem and resource group management features. This document describes how to install and configure the Java environment (see Chapter 3).
The Command Line Interface (CLI) allows you to perform Device Manager operations
by issuing commands from the system command line prompt. CLI communicates with and runs as a client of the Device Manager server. For further information on the CLI, see the HP StorageWorks XP Command View Advanced Edition software Device Manager CLI user guide.
The Device Manager supports third-party applications by providing an application

program interface (API) that developers can use to interface with the Device Manager server.
The Device Manager agent (recommended, optional) runs on a host that is attached to one or more storage subsystems, collects data on the configuration and utilization of the attached storage, and sends this information to the Device Manager server. Device Manager clients display this information once it is available on the server. For more information, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
24
Figure 1-1 XP Command View AE software Device Manager system components
1-4 Important terms and concepts

Device Manager users should be familiar with the following terms and concepts:
Array (parity) group: A group of hard disk drives (HDDs) that have identical capacity and are treated as one RAID unit. An array group contains user data and parity information, which ensures user data integrity in the event of a disk drive failure in the array group. Channel adapter/port controller (CHA): A Fibre Channel adapter in the storage subsystem that is equipped with one or more ports to establish connection with the host. For HP StorageWorks XP disk arrays, it is referred to as the channel adapter (CHA). Command device: A logical unit (LU) used exclusively for communicating with the XP RAID Manager software on the host to control copy operations. Copy pair: An XP Continuous Access Software or XP Continuous Access Journal Software copy pair consists of one primary volume (P-VOL) and one secondary volume (S-VOL) in different storage subsystems. An XP Snapshot copy pair for the XP24000/XP20000 or XP12000/XP10000/SVS200 consists of one P-VOL and from 1 to 64 V-VOLs. An XP Business Copy Software copy pair (layer 1) consists of one P-VOL and from 1 to 3 S-VOLs in the same storage subsystem. A layer-2 XP Business Copy Software cascade copy pair has one SP-VOL and from 1 to 2 S-VOLs in the same storage subsystem. Copy pair volume: Any volumes that make up a copy pair, including P-VOLs, S-VOLs, SPVOLs, and V-VOLs. DEVN: A number that is used to identify an LDEV that is used by a mainframe. Discrete/normal VDEV configuration: A configuration in XP1024/XP128 RAID5 7D+1P only that uses two parity groups (PGs) to create a virtual device (VDEV) array group in the Device Manager. A normal VDEV is created on a single parity group. HP StorageWorks XP Disk/Cache Partition: Provides the cache logical partition and storage logical partition functions (for XP12000/XP10000/SVS200). For details on these functions, see section 4-6 . Host: A computer system that uses storage in a storage subsystem. With Device Manager, you can group the WWNs or iSCSI names by which storage can be accessed, and define them as a single host. Hosts object: A display of the user-defined hosts in the Device Manager GUI and the detailed storage information for each host, including allocated capacity and storage groups in use. For 25
Overview of HP StorageWorks XP Command View Advanced Edition software Device Manager each host server, the Hosts object displays information about storage allocated to the host. The Hosts object is displayed in the navigation area of the Device Manager main window by selecting Resources and then Hosts in the Explorer menu.
Host storage domain: An existing host group on an XP24000/XP20000, XP12000/XP10000/SVS200 or XP1024/XP128 storage subsystem that is configured using the XP LUN Manager software for the storage subsystem. The Device Manager displays the host storage domain information and allows the user to change host storage domain names. When you reach the maximum number of host storage domains on a port, you must use another port for securing storage. The following shows the maximum number of host storage domains supported by each storage subsystem:
XP24000/XP20000 and HP XP12000 support a maximum of 255 host groups per port,
and 57,344 host groups for the entire storage subsystem.
HP XP10000 supports a maximum of 255 host groups per port, and 12,240 host groups
for the entire storage subsystem.
XP1024/XP128 supports a maximum of 128 host groups per port, and 8,192 host groups
for the entire storage subsystem.
iSCSI name: A unique name assigned to identify nodes when they are connected via iSCSI. iSCSI target: A node in the storage subsystem that is connected via iSCSI. LDEV: A logical device on a storage subsystem. An unallocated LDEV is not mapped to a LUN; therefore it has no access path. An allocated LDEV has one or more access paths (LUNs). Logical group: A user-defined group for managing storage. A logical group can contain both logical groups and storage groups. You can add storage to an empty logical group but not to a logical group that contains a subordinate logical group or storage group. Logical groups are displayed under the Logical Groups object, which is displayed in the navigation area of the Device Manager main window. Logical Groups object: A display of the user-defined logical groups in the Device Manager. The Logical Groups object is displayed in the navigation area of the Device Manager main window. The logical groups object can be expanded to display individual logical groups. The user-defined storage groups are displayed at the end of the logical groups, along with information about the storage allocated to each groups. The logical groups object can be structured as desired by the user for example, by platform, by organizational department, etc.) with logical groups in a hierarchical configuration. LUN group: A logical unit number (LUN) security group on an XP512/XP48 storage subsystem. Device Manager allows the user to manage LUN groups. LU/volume: A logical unit (LU) or volume on a storage subsystem. In most cases an LU, or volume, is the same as an LDEV. An exception is an XP LUN Expansion (LUSE) volume. Port: The CHA/port controller port where the cable from storage subsystem is connected. Primary volume (P-VOL): The source volume that is copied to another volume by XP Business Copy Software, XP Snapshot, XP Continuous Access Software, or XP Continuous Access Journal Software. Resource group: A user-defined set of resources that can be manipulated as a group. Only users with Admin permission can operate resource groups. A resource group can consist of hosts, logical devices (LDEVs), and logical groups. A user assigned to a resource group can view and manage only the resources of the assigned group. Resource groups are displayed in the Resource Group Administration dialog box. Secondary volume (S-VOL): The target volume onto which a P-VOL is copied by XP Business Copy Software, XP Snapshot, XP Continuous Access Software, or XP Continuous Access Journal Software.
26
Secondary-primary volume (SP-VOL): An XP Business Copy Software volume that is an SVOL in the top layer and a P-VOL in the second layer. When you use the XP Business Copy Software cascade function, you can create a copy pair (in the second layer) whose P-VOL is an S-VOL of another copy pair (in the top layer). Storage group: A user-defined set of paths (LUNs) that can be manipulated as a group. Adding storage to an empty logical group renders that group a storage group. The LUNs that share a storage group must physically reside in the same storage subsystem. A storage group cannot contain another storage group or logical group. Storage groups are displayed under the Logical Groups object, which is displayed in the navigation area of the Device Manager main window. Subsystems object: A display of the physical configuration information for the storage subsystems, such as: serial number, number and type(s) of ports, location and capacity of installed array groups, LDEVs and paths, and amount of cache memory. The Subsystems object is displayed in the navigation area of the Device Manager main window. THP pool: An area of a pool that stores THP (Thin Provisioning Software) volume data. THP pool volume: THP pool volumes make up the data storage area on a THP volume. THP volume: A virtual volume used for XP Thin Provisioning Software (THP). Volume path/LUN: A path to an LU in a storage subsystem. The volume path maps the LU to a port and an LU number (LUN). Each LU can have one or more paths, and each path can have different LUN security settings. The type of storage subsystem determines the number of logical paths that may be connected to each port.
XP24000/XP20000 supports no more than 2,048 paths per port via a Fibre Channel port. The XP12000/XP10000/SVS200 supports no more than 1,024 paths per Fibre Channel
port.
The XP1024/XP128 supports no more than 512 paths per Fibre Channel port. The XP512/XP48 supports no more than 256 paths per Fibre Channel port.
V-VOL: Logical duplicated volume of the XP Snapshot function consisting of physical data stored in the primary volume and differential data stored in the data pool. WWN (World Wide Name): A unique name assigned to identify the ports of a Fibre Channel host bus adapter on a physical host server. A bus adapter can have either one or two ports. WWN group: A WWN group on an XP512/XP48. Device Manager allows the user to manage WWN groups. XP Business Copy Software: The XP Business Copy Software feature enables users to copy volumes in the same storage subsystem. For details, see your XP Business Copy Software manual. XP Continuous Access Software: A feature that enables users to copy volumes in a different storage subsystem. For details, see the XP Continuous Access Software manual. XP Continuous Access Journal Software: The XP Continuous Access Journal Software feature enables users to asynchronously copy volumes between different storage subsystems. This feature provides the source and destination storage subsystems with logical devices (LDEVs), called journal volumes (JNL-VOL), which store the updates as journal data. For details about XP Continuous Access Journal Software, refer to the XP Continuous Access Journal Software manual. XP Disk/Cache Partition: Provides the logical cache partition and logical storage partition functions. For details on these functions, see section 4-6 . XP LUN Expansion (LUSE) device: A LUSE volume is a logical volume that consists of several logical units and that is larger than a standard LU. LUSE volumes can hold from 2 times to 36 times the capacity of a standard OPEN-x LU.
27
XP RAID Manager: The licensed software product that enables the user to perform XP Continuous Access Software and/or XP Business Copy Software operations by issuing commands from the host to the command device on the storage subsystem. For details about XP RAID Manager, see the XP RAID Manager manuals. XP Snapshot: The XP Snapshot feature (for XP24000/XP20000, XP12000/XP10000/SVS200 only) allows users to copy volumes in the same storage subsystem. For details, see the XP Snapshot manual.
Device Manager and the storage subsystems do not always use the same terminology. Table 1-1 shows some of the principal terms used by the Device Manager and their corresponding terms in the storage subsystems. Table 1-1 Device Manager and corresponding storage subsystem terms Device Manager
Port controller Host storage domain Array group XP Snapshot Continuous Access XP Journal
XP24000/XP20000 and XP1024/XP128 XP12000/XP10000/SVS200

CHA Host group CHA Host group
XP512/XP48
CHA Not applicable Parity group Not applicable Not applicable
VDEV (an area that subdivides VDEV (an area that a parity group) subdivides a parity group) XP Snapshot Not applicable
XP Continuous Access Journal Not applicable Software
1-5 Syntax conventions

Table 1-2 defines the syntax conventions used in this manual. An example of using these syntax conventions would be: StoreDatabase [temp|perm] (database-name ...) Table 1-2 Syntax conventions Font or Symbol
StoreDatabase database-name SD perm [ ] | ...
Usage
Enter code characters exactly as shown. Replace the italics with suitable text. Bold code-font characters indicate an abbreviation for a command. Underlining indicates a default value. Items enclosed in square brackets are optional. Only one of the options separated by a vertical bar can be used at one time. Ellipses (...) indicate that the item or items that are enclosed in parentheses() or square brackets[] and immediately precede the ellipses can be repeated. The items enclosed by parentheses are in the range to which | or ... are applied.
()
28

This chapter describes Device Manager operations:
User management and access restrictions (see section 2-1 ) Storage management operations (see section 2-2 ) Managing storage subsystems (see section 2-3 ) Link-and-launch operations (see section 2-4 ) Report operations (see section 2-5 ) System security operations (see section 2-6 ) Linkage with HP SIM (see section 2-7 )
2-1 User management and access restrictions

The Device Manager uses the common user management function provided by the XP Command View AE Suite to manage users. By handling combinations of resource groups and permissions set for each user, the common user management function provided by the XP Command View AE Suite can be used to manage user permissions and access to resources. For details on permissions, see section 2-1-1 , and for details on resource groups, see section 2-1-2 . For details on how to manage users and resource groups, see Chapter 6.
2-1-1 Permissions
The user management function that is common to all XP Command View AE Suite enables you to set the following permissions for each user:
The User Management permission common to all XP Command View AE Suite Operation permissions for Device Manager Permissions for XP Command View AE Suite other than Device Manager For details on the permissions for XP Command View AE Suite other than Device Manager, see the manual for the relevant product.
Permissions relating to Device Manager users are as follows:
The User Management permission common to all XP Command View AE Suite Operation permissions for the Device Manager.
Table 2-1 lists the permissions relating to Device Manager users.
29
Table 2-1 List of permissions Classification

Device Manager operation permissions
Permission
Admin
Description
Allows the user to use the resource group management function with the available range of resources. When you set the Admin permission for a user, the Modify permission and the View permission are set at the same time. Allows the user to operate the available range of resources. When you set the Modify permission for a user, View permission is set at the same time. Allows the user to view the available range of resources. This permission is exclusively for use with Device Manager agents. A user with Peer permission cannot log in from web client to Device Manager. Furthermore, you cannot allocate a resource group to a user who has Peer permission. You cannot set this permission in combination with any other permission except the User Management permission. Allows the users of XP Command View AE Suite to use the user management function. You cannot allocate a resource group to a user who has User Management permission only. Can be set in combination with any of the Device Manager operation permissions.
Modify
View Peer
The User User Management* Management permission (common to all XP Command View AE Suite)
*
To set the User Management permission common to all XP Command View AE Suite, click User Management and then set the Admin permission on the GUI of the product
Note that there are two Admin permissions: the Admin operation permission and the Admin User Management permission. To avoid confusion, this manual uses the following terms:
Admin permission refers to the Admin operation permission for Device Manager. User Management permission refers to the Admin User Management permission, which is common to all XP Command View AE Suite.
2-1-2 Resource groups

The Device Manager supports both the All Resources resource group and a user-defined resource group.
All Resources This resource group is predefined in the Device Manager. The All Resources resource group includes all Device Manager resources (logical groups, hosts, and LDEVs). A user who is assigned this resource group can access all Device Manager resources.
User-defined resource group The user can define which resources are to be held in a group. A user who is assigned to a user-defined resource group can access only the resources defined in that group. Therefore some functions are not available for the user. When a user who is assigned a user-defined resource group logs in, the following menus are not displayed in the explorer menu:
ResourcesSubsystems menu
30
Alerts menu Reports menu

Only a user who has Admin permission can create a resource group or allocate a resource group to a user. For details on how to manage resource groups, see section 6-3 . Resource groups are closely related to logical groups. For example, suppose that there is a logical group B under logical group A. If logical group A is allocated to resource group A and logical group B is allocated to resource group B, resource group B will be lower in the hierarchy than resource group A. The users of resource group A can access the resources (logical group, hosts, and LDEVs) in both resource groups A and B.
2-1-3 Built-in accounts

Device Manager contains two predefined built-in accounts: the System accounts and the HaUser accounts. The System account is a built-in account common to all XP Command View AE Suite. With the System account, you can use all the functions provided by the Device Manager and the other XP Command View AE Suite and you can access all resources managed by the applications. When you first log in after installing Device Manager, log in with the System account and, if necessary, set up a user account that has the User Management permission and a user account that has the Admin permission for the Device Manager. The default password for the System account is manager. To prevent unauthorized access, we recommend that you change the default password for the System account. You cannot delete the System account or change the permissions associated with the System account. The HaUser account is the default user for Device Manager agents. The Peer permission is set for the HaUser account. The default password for the HaUser account is haset. If you have changed the password for the HaUser account, you need to change the settings for the Device Manager agent. For details on how to change the settings for the Device Manager agent, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
2-1-4 Security enhancement at login

In order to enhance security when a user logs in, the Device Manager enables the system administrator to set security options. The security options at login are:
Locking User Accounts options In the Device Manager, you can suppress the login operation of a particular user by manually locking the user account. You can also set up this function so that it automatically locks a user account if an incorrect password is entered repeatedly for that account. When a user account is locked, the user cannot log in to any of the XP Command View AE Suite until the user account is unlocked. For details on how to lock or unlock a user account, see section 6-2-5 . For details on how to set up automatic locking of user accounts, see section 6-4-2 .
Setting Password Conditions options To prevent users' passwords from being guessed by a third party, the Device Manager enables you to specify the minimum number of characters and the combination of characters that can be used for a password. For details on how to set the password conditions, see section 6-4-1 .
Setting a Warning Banner message options As a security measure at login, the Device Manager allows you to display a message on the login window (Figure 2-1 shows an example of a warning banner message). For details on how to set a warning message, see section 6-4-3 . 31
Figure 2-1 Example of a warning banner message
2-2 Storage management operations

The Device Manager enables you to manage storage resources in the following groups on subsystems that are added to the Device Manager.
Storage groups. The Device Manager enables you to create and manage groups of LUNs (volume paths). The LUNs assigned to a storage group can then be manipulated as a group. Storage groups must contain logical devices that share a storage subsystem. A storage group can contain only LUNs; it cannot contain other groups. Logical groups. The Device Manager enables you to create and manage one or more storage groups under a logical group. A logical group can contain storage groups that contain LUNs or other logical groups. This additional level of grouping creates a file-system approach to storage management and enables you to tailor your Device Manager system to your operational environment. Resource groups. The Device Manager enables you to create and manage one or more resource groups. Each resource group is associated with one or more logical groups, hosts, and LDEVs. When you create a user and assign a user-defined resource group to the new user, this user will can access only the resources (logical groups, hosts, LDEVs) associated with that resource group.
2-3 Managing storage subsystems

This section lists and provides an overview of the storage subsystems functions supported by Device Manager web client.
Functions supported for each storage subsystem (see section 2-3-1 ). Overview of supported functions (see section 2-3-2 ).
2-3-1 Functions supported for each storage subsystem

Device Manager web client allows you to view information and change settings for XP24000/XP20000, XP12000/XP10000/SVS200, XP1024/XP128, and XP512/XP48. For volumes in storage subsystems, you can also perform data management operations, such as configuring LUN security and replicating or backing up data.
32
NOTE: You can perform data management operations only if the data management function is installed and available on the storage subsystem. Table 2-2 lists the functions supported by web client for each storage subsystem. Table 2-2 Functions for each storage subsystem that are supported by web client Function Storage Subsystem XP24000/ XP20000
Assignment and deletion of LUNs Setting and releasing of LUN security for LUNs Management of logical groups Y1 Y Y
XP12000/ XP10000/ SVS200

Y1 Y Y Y Y Y Y Y Y Y Y2,3 Y3 Y Y
3 3
XP1024/ XP128
Y1 Y Y Y Y Y Y Y Y Y Y2 Y Y Y Y --Y Y Y Y Y ----Y Y
XP512/ XP48
Y1 Y Y Y --Y Y Y Y Y2 Y Y Y Y Y Y Y Y Y Y Y ----Y --
Configuring LUSE volumes while LUNs are being Y allocated Configuring LUSE volumes using LDEVs for which LUNs are allocated Configuring or releasing LUSE volumes when using LDEVs for which LUNs are not allocated LUN scanning Detection and removal of storage subsystems Acquisition of storage subsystem information Detailed information display and configuration modification of storage subsystems Creation and deletion of LDEVs Modification of port attributes Modification of Fibre Channel adapter attributes Configuration of command devices Setting of security for command devices Management of LUN groups Management of WWN groups Management of host information Management of host volume information Host refresh function Reporting operations Alert management Viewing of CLPR information Modification of CLPR information Viewing of SLPR information Modification of SLPR information Viewing of mainframe volume information Viewing of XP Data Retention Utility information Y Y Y Y Y Y Y2,3 Y3 Y Y
3 3
Y3 --Y Y Y Y Y Y Y
3
Y3 --Y Y Y Y Y Y Y
3
Y Y Y Y
3
Y Y
3
Y Y
33
Table 2-2 Functions for each storage subsystem that are supported by web client Function Storage Subsystem XP24000/ XP20000
Viewing of external volume information Y
XP12000/ XP10000/ SVS200

Y --Y Y Y Y Y N Y Y
XP1024/ XP128
---Y Y Y Y -----
XP512/ XP48
---Y Y Y Y -----
Viewing of THP volume information and THP pool Y information Configuring, changing, or deleting THP volumes and THP pools Y
Viewing of XP Business Copy Software copy pair Y information Creation, status modification, and deletion of XP Business Copy Software copy pairs Viewing of XP Continuous Access Software copy pair information Creation, status modification, and deletion of XP Continuous Access Software copy pairs Viewing of XP Snapshot copy pair information Creation, status modification, and deletion of XP Snapshot copy pairs Viewing of XP Continuous Access Journal Software copy pair information Creation, status modification, and deletion of XP Continuous Access Journal Software copy pairs Y Y Y Y N Y Y
Legend: Y = The function is supported. -- = The function is not present in the storage subsystem. N = The function is present in the storage subsystem, but is not supported by Device Manager. 1 LUNs can be assigned only to open volumes and HRX intermediate volumes. 2 The LDEV to be created must be an open volume. 3 This function can be performed in XP Remote Web Console when Physical View is started.
2-3-2 Overview of supported functions

This subsection describes the functions supported by Device Manager web client.
2-3-2-1 Assignment and deletion of LUNs

Device Manager web client enables you to set a volume path to an LDEV in a storage subsystem to allocate a LUN or unallocate a LUN (see sections 7-6-2 and 7-6-5 ).
2-3-2-2 Setting and releasing of LUN security for LUNs

Device Manager web client enables you to secure or unsecure a LUN in storage (see section 7-64 ). If LUN security is set, you will not be able to access the storage from a WWN of a host that is not set as LUN security. The unit for which LUN security is set differs depending on the storage subsystem as follows:
When the storage subsystem is XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128, LUN security is set for individual host storage domains. When the storage subsystem is XP512/XP48, LUN security is set for individual ports.
34
2-3-2-3 Management of logical groups

Device Manager web client enables you to use logical groups to manage LUNs allocated to storage. It also enables logged-in users to view information about logical groups that they can access, and to edit the logical group properties (see section 7-4 ).
2-3-2-4 Configuring LUSE volumes while LUNs are being allocated

Device Manager enables you to create a LUSE volume when allocating a LUN to an LDEV (see section 7-6-2 ). You cannot create a LUSE volume from an LDEV to which a LUN has already been allocated.
2-3-2-5 Configuring LUSE volumes when using LDEVs for which LUNs are allocated
When the storage subsystem is XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128, Device Manager web client enables you to create a LUSE volume by using an LDEV to which a path is allocated as the representative LDEV (see section 8-6-2 ).
2-3-2-6 Configuring or releasing LUSE volumes when using LDEVs for which LUNs are not allocated
When the storage subsystem is XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128, Device Manager web client enables you to create a LUSE volume from LDEVs to which no paths managed are allocated (see section 8-6-3 ).
2-3-2-7 LUN scanning

If you perform a LUN Scan, Device Manager detects LDEVs to which paths have already been assigned, and stores the path information in logical groups that were automatically created according to the connected port and the set security (see section 8-3 ).
2-3-2-8 Detection and removal of storage subsystems

Device Manager web client enables you to add to Device Manager storage subsystems that you want to manage. If you add a storage subsystem, the Device Manager server will detect the storage subsystem that was added to the network of the Device Manager system (see Chapter 10).
2-3-2-9 Acquisition of storage subsystem information

Device Manager web client enables you to view information about the managed storage subsystems. The displayed information about the storage subsystems includes the following items: the name, type, serial number, IP address, cache size, microcode level, capacity, and date and time when the refresh operation was last performed (see section 10-1-3 ).
2-3-2-10 Detailed information display and configuration modification of storage subsystems

Device Manager web client enables you to view the detailed configuration information or modify the configuration for each storage subsystem managed by Device Manager. This function can be performed in Physical View. For details how to start Physical View, see section 10-2 .
2-3-2-11 Creation and deletion of LUNs

Device Manager web client enables you to create new LDEVs or delete the existing LDEVs. For details on creating and deleting LDEVs of XP24000/XP20000 and XP12000/XP10000/SVS200, see the XP Remote Web Console manual.
35
Device Manager operations For details on creating and deleting LDEVs of XP1024/XP128 and XP512/XP48, see section 10-4-3 .
2-3-2-12 Modification of port attributes

Device Manager web client enables you to change port attributes of the storage subsystem. For details on how to configure ports on XP24000/XP20000 or XP12000/XP10000/SVS200, see the XP Remote Web Console manual. For details on how to configure ports on XP1024/XP128 or XP512/XP48, see section 10-3-1 .
2-3-2-13 Modification of Fibre Channel adapter attributes

For XP24000/XP20000, XP12000/XP10000/SVS200, XP1024/XP128, and XP512/XP48, Device Manager web client enables you to change the Fibre PCB mode (the operating mode of the Fibre Channel port) for the Fibre Channel adapters. For details on how to change the speed mode for the Fibre Channel adapters on XP24000/XP20000 or XP12000/XP10000/SVS200, see the XP Remote Web Console manual. For details on how to change the speed mode for the Fibre Channel adapters on XP1024/XP128 or XP512/XP48, see section 10-3-4 .
2-3-2-14 Configuration of command devices and setting of the command device security
Device Manager web client enables you to set an LDEV in the storage subsystem as a command device and set security for the command device. For details on how to set a command device on XP24000/XP20000 or XP12000/XP10000/SVS200, see the XP Remote Web Console manual. For details on how to set a command device on XP1024/XP128 or XP512/XP48, see section 10-4-5 .
2-3-2-15 Management of LUN groups and WWN groups

Device Manager web client enables you to create, modify, or delete LUN groups and WWN groups (see section 10-3-2 ).
2-3-2-16 Management of host information and host volume information

Device Manager web client enables you (the logged-in user) to view and modify the list of hosts for which you have access permissions and the host properties for each host. It also enables you to view information about the volumes allocated to a host (see sections 9-5 and 9-6 ).
2-3-2-17 Host refresh function

Device Manager web client enables you to update volume information about a host and copy pair information about a volume to the latest status (see section 9-8 ).
2-3-2-18 Reporting operations

Device Manager web client enables you to display, in HTML format, information about volumes in storage subsystems and user management, and to output that information in CSV format (see Chapter 11).
2-3-2-19 Alert management

Device Manager web client enables you to display SNMP traps, errors, and other conditions for each of the storage subsystems managed by the Device Manager server (see section 5-4 ). 36
2-3-2-20 Viewing and modification of CLPR information

When XP24000/XP20000 or XP12000/XP10000/SVS200 is used, Device Manager web client enables you to view and change the CLPR information for an LDEV. For XP24000/XP20000 and XP12000/XP10000/SVS200, Device Manager web client uses XP Disk/Cache Partition to partition a cache in the storage subsystem. For details on XP Disk/Cache Partition, see section 4-6 .
2-3-2-21 Viewing and modification of SLPR information

When XP24000/XP20000 or XP12000/XP10000/SVS200 is used, Device Manager web client enables you to view and change the SLPR information. For XP24000/XP20000 or XP12000/XP10000/SVS200, Device Manager web client uses XP Disk/Cache Partition to partition the resources inside the storage subsystem. For details on XP Disk/Cache Partition, see section 4-6 .
2-3-2-22 Viewing mainframe volume information

Device Manager web client enables you to view the mainframe volume information (see section 8-24 ).
2-3-2-23 Viewing of XP Data Retention Utility information

XP Data Retention Utility protects storage subsystem volumes by setting the protection mode for each volume. Device Manager web client enables you to view the XP Data Retention Utility information.
2-3-2-24 Viewing of external volume information

Device Manager web client enables you to view the information of other storage subsystems connected by using XP External Storage Software, as external volume information (see section 4-5 ).
2-3-2-25 Viewing of THP volume information and THP pool information

When XP24000/XP20000 is used, Device Manager web client enables you to view, as the LDEV information, detailed information about the THP volume and THP pool that are used in XP Thin Provisioning Software. In addition, Device Manager web client enables you to view the consumed capacity of the THP volume to check the usage status of the THP volume. For details about the XP Thin Provisioning Software function of XP24000/XP20000, see the manual for XP Thin Provisioning Software.
2-3-2-26 Configuring, changing, or deleting THP volumes and THP pools

When XP24000/XP20000 is used, Device Manager web client enables you to configure, change, or delete the THP volume and THP pool that are used in XP Thin Provisioning Software(see section 88 ).
2-3-2-27 XP Business Copy Software

XP Business Copy Software makes a data copy inside a storage subsystem.
2-3-2-28 XP Continuous Access Software

XP Continuous Access Software makes a data copy between different storage subsystems. It enables you to perform a synchronous or asynchronous remote copy.
37
2-3-2-29 XP Snapshot
XP Snapshot copies logical snapshot data inside a storage subsystem. IMPORTANT: XP24000/XP20000 or XP12000/XP10000/SVS200 is used, use XP RAID Manager to operate XP Snapshot copy pairs.
2-3-2-30 XP Continuous Access Journal Software

XP Continuous Access Journal Software enables you to perform an asynchronous remote copy between different storage subsystems. XP Continuous Access Journal uses updates created in a journal volume to make a data copy.
2-4 Link-and-launch operations

The Device Manager link-and-launch feature enables administrators to move easily across storage management software for a full view of their storage resources. For information on the requirements for link-and-launch operations, see section 4-2 . The Device Manager provides link-and-launch integration with the following software applications:
HDLM (see section 5-6-1 ) XP Provisioning Manager software (see section 5-6-2 ) XP Tiered Storage Manager software (see section 5-6-3 ) XP Replication Monitor software (see section 5-6-4 ) XP Remote Web Console (see section 5-6-5 ) HP Storage Essentials (see section 5-6-6 ) NAS Manager (see section 5-6-7 )
2-5 Report operations

The Device Manager provides a built-in reporting function that enables users to generate reports in both HTML format and comma-separated value (CSV) format (see Chapter 11). The Device Manager reports include:
Physical configuration of storage subsystem report: Physical configuration of the storage subsystems being managed by Device Manager Storage utilization by host report: Storage utilization, organized and presented by host Storage utilization by logical group report: Storage utilization, organized and presented by logical group Users and resource groups report: Resource groups of Device Manager, and users who are assigned to those resource groups Detailed Array Reports: Detailed information about the LDEVs managed by Device Manager.
2-6 System security operations

The Device Manager can be deployed securely in a variety of operational environments, including private LAN, virtual private network (VPN), corporate intranet, and even public internet. The security features for Device Manager communications (between the web client and the server, for example) can be customized for your operational environment. The Device Manager provides an end-to-end security context between the user and the Device Manager server that prevents message tampering and provides privacy, user authentication, and
38
Device Manager operations non-repudiation. Messages between the Device Manager web client and the Device Manager server are secured when the server is running in security mode 2 (SSL/TSL). The Common Component Single Sign-On feature (see section 1-3 ) maintains user authentication across XP Command View AE Suite software and plug-ins. The Common Component integrated logging feature provides a common log repository for the various logs of the XP Command View AE Suite software. For more information on Device Manager security operations, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide.
2-7 Linkage with HP SIM

You can start Device Manager from the HP SIM (HP Systems Insight Manager) menu without logging in again. Permissions for XP Command View AE Suite will be determined by the tools authenticated by HP SIM users. To start XP Command View AE Suite other than Device Manager, you first start Device Manager from HP SIM and then start the other products from the Dashboard menu. For details about how to start Device Manager from HP SIM and how to map the permissions when HP SIM users use XP Command View AE Suite, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide.
39

This chapter describes the requirements for web client operations, preparations for accessing the web client, and the requirements and procedures for installing the Java environment.
Requirements for web client operations (see section 3-1 ) Preparing to access the web client (see section 3-2 ) Installing the Java software environment (see section 3-3 ) Configuring Java software for client/server operations (see section 3-4 ) Upgrading the Java GUI and clearing the cache (see section 3-5 ) Setting up secure communication with Device Manager (see section 3-6 )
3-1 Requirements for web client operations

The requirements for Device Manager web client operations are:
Device Manager server: The Device Manager server must be installed, configured, and fully operational. For instructions, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. Platform: Device Manager 5.9 supports the following operating systems for the web client:
Microsoft Windows 2000 (with Service Pack 4) Microsoft Windows XP (with Service Pack 1 or 2) Microsoft Windows Server 2003 (with no Service Pack or Service Pack 1 or 2) (x86
processor version only)
Windows Server 2003 R2 (with no Service Pack or with Service Pack 2) (x86 processor
version only)
Windows Vista Solaris 8 (SPARC edition) Solaris 9 (SPARC edition) Solaris 10 (SPARC edition) or Solaris 10 (x64 edition) Solaris 10 (x64 edition) is supported only when the Sun Fire x64 Servers hardware is used.
HP-UX 11i v1 (PA-RISC), HP-UX 11i v2 (PA-RISC or IPF), or HP-UX 11i v3 (IPF) Red Hat Enterprise Linux AS 4 Update 4 (x86) or Red Hat Enterprise Linux ES 4 Update
4 (x86) Monitor resolutions XGA and higher. NOTE: If the OS is Solaris 10, the use of XP Remote Web Console for XP1024/XP128 is not supported.
Web Browser for HTML GUI: Device Manager 5.9 supports the following web browsers for the web client:
For Windows 2000: Internet Explorer 6.0 For Windows XP (with Service Pack 1): Internet Explorer 6.0 For Windows XP (with Service Pack 2): Internet Explorer 6.0 and Internet Explorer 7.0 For Windows Server 2003 (with no Service Pack): Internet Explorer 6.0
40
For Windows Server 2003 (with Service Pack 1 or 2): Internet Explorer 6.0 and Internet
Explorer 7.0
For Windows Server 2003 R2 (with no Service Pack or with Service Pack 2): Internet
Explorer 6.0 and Internet Explorer 7.0
For Windows Vista: Internet Explorer 7.0 For Solaris 8: Mozilla 1.4 For Solaris 9: Mozilla 1.4 and Mozilla 1.7 For Solaris 10: Mozilla 1.7 For HP-UX 11i v1 or HP-UX 11i v2: Mozilla 1.7.8.00 and Mozilla 1.7.12.01 For HP-UX 11i v3: Mozilla 1.7.13.01 For Linux: Mozilla 1.4.1
NOTE: If you want to use web client for IPv6 connections in an environment where both IPv6 and IPv4 are used, the combination of OS and web browser must be one of the following: Windows Vista and Internet Explorer 7.0 Windows Server 2003 (with Service Pack 2) and Internet Explorer 6.0 Windows Server 2003 R2 (with Service Pack 2) and Internet Explorer 6.0 HP-UX 11i v2 and Mozilla 1.7.12.01 Solaris10 and Mozilla 1.7 Linux and Mozilla 1.4.1
Environment-configuration issues:
Environment variable setting for the web client in Solaris, HP-UX, or Linux: When
the web client is used in Solaris, HP-UX, or Linux, the PATH environment variable must contain the entry for the Mozilla installation directories to enable launching of the help and report functions and other applications. NOTE: When the web browser is set as noted below, characters might be displayed on top of each other (that is, two or more characters might appear in the same space on the screen) in the web client. In Internet Explorer, the character size is set to Largest. In Mozilla, the character size is set to a value greater than 120%. In Internet Explorer version 7.0, the enlargement level is a value other than 100% (default).
In a Solaris environment: Make sure that the web browser language setting and the Xterminal setting are the same. If they are different, the title bar character strings might be displayed incorrectly.
In a non-Windows environment: If you display the web client GUI reference with
Mozilla, italics and bold might be displayed incorrectly.
Third-party cookie setting: The web browser you use to view the HP XP Command
View AE software web client must be configured to allow third-party cookies; errors can occur if the browser is configured to block cookies.
Java execution environment: The Device Manager web client requires the following
Java software environment. Java Web Start (JWS) is automatically installed when Java Runtime Environment (JRE) is installed:
In Windows XP (with Service Pack 1), Solaris 8, or Solaris 9:

JRE version 1.4.2_xx (where xx = 06 or later)*1 or version 5.0 (Update 7 or later) JWS version 1.4.2_xx (where xx = 06 or later)*1 or version 5.0 (Update 7 or later)
In Windows 2000, Windows XP (with Service Pack 2), Windows Server 2003 or
Windows Server 2003 R2: 41
Installing the Device Manager web client JRE version 1.4.2_xx (where xx = 06 or later)*1, version 5.0 (Update 7 or later) or version 6.0*2 JWS version 1.4.2_xx (where xx = 06 or later)*1, version 5.0 (Update 7 or later) or version 6.0*2
In Solaris 10:
JRE version 1.4.2_xx (where xx = 12 or later)*1, version 5.0 (Update 7 or later) or version 6.0 JWS version 1.4.2_xx (where xx = 12 or later)*1, version 5.0 (Update 7 or later) or version 6.0
In Windows Vista:
JRE version 6.0*2 JWS version 6.0*2
In HP-UX:
JRE version 1.4.2_xx (where xx = 06 or later)*1 or version 5.0.03 or later JWS version 1.4.2_xx (where xx = 06 or later)*1 or version 5.0.03 or later If the system on which HP-UX operates uses a Dual-Core Intel Itanium 2 Processor for the CPU, use JRE version 1.4.2_xx (xx: 10 or later) or JRE version 5.0.03 or later, which comes with HP-UX (released in June 2006 or September 2006) that supports the processors.
In Linux:
JRE version 1.4.2_xx (where xx = 06 or later)*1 JWS version 1.4.2_xx (where xx = 06 or later)*1 NOTE: *1 HP recommends you use the latest version for "xx". *2 In Windows, JRE version 6.0 is supported only when Internet Explorer 7.0 is used. NOTE: If the OS is Windows, you must use JRE version 5.0 or later to establish IPv6 connections with the Device Manager server. If you are using JRE version 1.4.2_xx, you cannot start the Java GUI.
Device Manager agent: (optional but recommended) The Device Manager agent is recommended, but not required, for Device Manager operations. If the Device Manager agent is installed, Device Manager will display usage and file system information for the storages assigned to the host, and statuses of the copy pairs managed by the host. For more information, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide. Storage subsystems: Before adding a storage subsystem to the Device Manager using the web client (or another client), make sure that the storage subsystem is configured for Device Manager operations. For subsystem configuration requirements, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide.
IMPORTANT: The Device Manager displays mainframe volumes (such as 3390-3) but does not allow you to manage the volumes.
Host bus adapters (HBAs): For information on HBAs required for storage subsystems, see the Device Manager release notes. Link-and-launch functionality: The Device Manager web client provides link-and-launch functionality with several other software applications, such as XP Remote Web Console and HDLM. See section 4-2 for the requirements for Device Manager link-and-launch operations.
42
3-2 Preparing to access web client

Before accessing the Device Manager web client software, complete the following tasks: 1. Install the Device Manager server: Make sure that the Device Manager server has been installed and configured properly as described in the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. NOTE: Device Manager server installation includes installation of the Common Component.
Copy pair operations If you plan to perform copy pair operations (XP Business Copy Software, XP Continuous Access Software, XP Snapshot, or XP Continuous Access Journal Software) using Device Manager, install the XP RAID Manager software on each host that manages copy pairs. For details on the requirements, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide.
2. Establish the Device Manager server address: Write down the URL (IP address and/or host name) of the Device Manager server and the port specified in the Server properties file (default = 23015). You will need this information to log in to the Device Manager server. NOTE: If you cannot connect to the Device Manager server home page, see the troubleshooting information in Table 12-1. 3. Install the Device Manager agent (optional) : The Device Manager agent is optional. If you will be using it, install it on the applicable host(s). For details, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide. 4. Configure a browser with pop-up blocking enabled: When using Device Manager on a browser for which pop-up blocking is enabled, configure the browser so that pop-ups of the Device Manager server are not blocked. For example: When using Internet Explorer for Windows XP (Service Pack 2):
Select the Tools menu and then Internet Options. In the Internet Options dialog box,
click the Security tab. Add the URL for the Device Manager server in the Trusted Sites box. Enter one of the following URLs, in the format shown: For communicating with the HBase Storage Mgmt Web Service of Device Manager server: http://Device-Manager-server-address:port-number/DeviceManager/ where: Device-Manager-server-address = IP address or host name of the Device Manager server port-number = port number of the HBase Storage Mgmt Web Service - For communicating with the Device Manager server: http://Device-Manager-server-address:port-number/ where: Device-Manager-server-address = the IP address or host name of the Device Manager server port-number = the port number of the Device Manager server Enter the appropriate value to specify the default value for the port number for secure socket layer (SSL) and/or non-SSL ports: For non-SSL: http://Device-Manager-server-address:23015/DeviceManager/ http://Device-Manager-server-address:2001/ For SSL: 43
Installing the Device Manager web client https://Device-Manager-server-address:23016/DeviceManager/ https://Device-Manager-server-address:2443/
When a pop-up is blocked and a warning message is displayed, select Always Allow
Pop-Ups From This Site. 5. For Internet Explorer security: Make sure the following settings are configured on the browser that uses the web client.
Run ActiveX controls and plug-ins is set to Enable. Script ActiveX controls marked safe for scripting is set to Enable. Active scripting is set to Enable. Launching programs and files in an IFRAME is set to Prompt or Enable. Submit non-encrypted form data is set to Prompt or Enable. For Internet Explorer 7.0, Allow websites to prompt for information using scripted windows is set to Enable.
File download is set to Enable.

6. Configuring the Internet Explorer 7.0 browser. When Internet Explorer 7.0 is used, in When a pop-up is encountered, you must select a radio button other than Always open pop-ups in a new tab. If Always open pop-ups in a new tab is selected, the window might be displayed behind another window. 7. Configuring the firewall. If a firewall is set between a machine where web client runs and the Device Manager server, you must configure the firewall so that the port number of the Device Manager server and javaws.exe (to be used by Java GUI) can be used. The default port number of the Device Manager server is 2001 (for non-SSL communication) or 2443 (for SSL communication).
3-3 Installing the Java software environment

The Device Manager uses client-server architecture to support application distribution management. This web-distribution framework is used to automatically update the Java GUI on a user's computer system. IMPORTANT: To host Device Manager web client, the Java 2 Runtime Environment (JRE) and Java Web Start (JWS) software products must be installed first. The Java Web Start software enables you to launch Java-based applications like the Java GUI directly from the web. NOTE: If the Java GUI is already installed and you have since then upgraded the version of the Device Manager, see section 3-5-1 for information on upgrading your version of the Java GUI. To install JRE and JWS: 1. If the necessary version of JRE comes with OS, use the supplied installer. If not supplied, download the platform-specific JRE installer. You can use the Device Manager Software Deployment dialog box to access the websites of vendors that provide a JRE. For details on the Device Manager Software Deployment dialog box, see section 5-7 . 2. Read the installation instructions and release notes for JRE provided on the website. 3. Install the JRE software using the JRE installer. Make sure that you read the Readme file for the JRE software. NOTE: Installing JRE automatically installs JWS. IMPORTANT: If the JRE version required for web client is not installed, attempting to display a
44
Installing the Device Manager web client Java GUI on web client starts the downloading of the latest JRE version. Install the latest version according to the displayed instructions. When installation is complete, the Java GUI appears. If JRE has been installed before the installation of the latest version, the settings of the newly installed JRE inherit the settings of the old JRE. However, you must configure Java Web Start (JWS) so that the appropriate version of JRE is used. For details about how to configure JWS, see section 3-4-3 . NOTE: If you use the Java GUI in Windows, do not specify a directory name that contains an exclamation mark (!) for the JWS cache directory. If such a directory name is specified, an error will occur during initialization of the Device Manager Java GUI, and the Java GUI will not be able to start. In the default settings for JWS, the cache directory includes the user's account name. Therefore, if the account name you use to log in to Windows contains an exclamation mark, a directory name that contains an exclamation mark will be set for the JWS cache directory. In this case, you need to change the setting of the cache directory by using the JWS control panel.
3-4 Configuring Java software for client/server operations

You can configure a Java environment using Java Web Start (JWS). You must configure the software as follows:
Set up the proxy (see section 3-4-1 ) Set up the log output (see section 3-4-2 ) Set up JWS when different JRE versions have been installed (see section 3-4-3 )
3-4-1 Setting up the proxy

You must set up the Java Web Start proxy in accordance with the method used to access the Device Manager server. The following methods are used to access the Device Manager server:
Accessing the Device Manager server and other applications without a proxy Accessing the Device Manager server via a proxy Accessing the Device manager server without a proxy and accessing other applications via a proxy
The following subsections explain the proxy setup method for each version of JWS and the method used to access the Device Manager server.
3-4-1-1 For Java Web Start 1.4.2_xx

The proxy setup methods for Java Web Start 1.4.2_xx are described below. To access the Device Manager server and other applications without a proxy: 1. Start the Java Web Start application manager. 2. Select the File menu, and select Preferences. 3. In the Java Web StartPreferences window, click the General tab. 4. Select None. 5. Click the OK button to accept the settings and exit the Java Web Start Application Manager. To access the Device Manager server via a proxy: 1. Start the Java Web Start application manager. 2. Select the File menu, and select Preferences.
45
Installing the Device Manager web client 3. On the Java Web StartPreferences panel, select the tab. 4. Select the method to be used to set up the proxy.
If the proxy setting is enabled in the web browser and it is also set to access the Device
Manager server via a proxy: Select the Use browser settings radio button.
To set up a proxy manually:

Select the Manual radio button and then enter values in the following items: HTTP Proxy: IP address or name of the proxy server HTTP Port: Port number of the proxy server 5. Click the OK button, and exit the Java Web Start application manager. To access the Device Manager server without a proxy and access other applications via a proxy: 1. Start the Java Web Start application manager. 2. Select the File menu, and select Preferences. 3. On the Java Web StartPreferences panel, click the General tab. 4. Select the method to be used to set up the proxy.
Manager server without a proxy: Select the Use Browser radio button.

Select the Manual radio button and then enter values in the following items. HTTP Proxy: IP address or name of the proxy server HTTP Port: Port number of the proxy server No Proxy Hosts: IP address or name of the Device Manager server 5. Click the OK button, and exit the Java Web Start application manager.
3-4-1-2 For Java Web Start 5.0 and 6.0

The proxy setup methods for Java Web Start 5.0 or 6.0 are described below. To access the Device Manager server and other applications without a proxy: 1. Start the Java Control Panel. 2. From the General tab, click the Network Settings button. The Network Settings window opens. 3. In the Network Settings window, select Direct connection. 4. In the Network Settings window, select the OK button. 5. In the Java Control Panel, click the OK button to exit the panel. To access the Device Manager server via a proxy: 1. Start the Java Control Panel. 2. From the General tab, click the Network Settings button. The Network Settings window opens. 3. In the Network Settings window, select the method to be used to set up a proxy.
Manager server via a proxy: Select the Use browser settings radio button.

Select the Use proxy server radio button and then enter values in the following items:
46
Installing the Device Manager web client Address: IP address or name of the proxy server Port: Port number of the proxy server
If an automatic proxy configuration script is enabled in the web browser and it is also set
to access the Device Manager server via a proxy: Select the Use automatic proxy configuration script radio button and then enter a value in the following item: Script location: Same script name and path as for the web browser. 4. In the Network Settings window, click the OK button. 5. In the Java Control Panel, click the OK button and exit the panel. To access the Device Manager server without a proxy and access other applications via a proxy: 1. Start the Java Control Panel. 2. From the General tab, click the Network Settings button. The Network Settings window opens. 3. In the Network Settings window, select the method to be used to set up the proxy.
Manager server without a proxy: Select the Use browser settings radio button and then proceed to step 7.

Select the Use proxy server radio button, enter values in the following items and then proceed to step 4: Address: IP address or name of the proxy server Port: Port number of the proxy server 4. Click the Advanced button. The Advanced Network Settings window opens. 5. In the Advanced Network Settings window, for Exceptions, enter the IP address or the name of the Device Manager server. 6. In the Advanced Network Settings window, click the OK button. 7. In the Network Settings window, click the OK button. 8. In the Java Control Panel, click the OK button and exit the panel.
3-4-2 Setting up the log output

Java Web Start (JWS) 1.4.2_xx enables you to output to a log file the messages that are sent to the standard output. You can output the Java GUI logs to a file by using this function and setting the properties for the client in the Device Manager server. For further information on property settings for clients in Device Manager, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. JWS can also collect the logs generated when you launch HDLM from the Device Manager web client (see section 2-4 ). To collect logs, you must set up the log output option in Java Web Start. To set up the log output option in Java Web Start 1.4.2_xx: 1. Start the Java Web Start Application Manager. 2. Select the File menu, and select Preferences. 3. On the Java Web StartPreferences window, click the Advanced tab. 4. Select the Show Java Console box to display the messages that are output to the log. This setting is optional. 5. In the Output Options box, select the Log Output check box and then enter the log file name in the Log File Name field. This setting is required.
47
Installing the Device Manager web client To enter the log file name, either type the desired file name in the Log File Name field, or click the Choose Log File Name button to select an existing log file name. 6. Click the OK button to save your changes, and exit the Java Web Start Application Manager.
3-4-3 Setting up Java Web Start

JWS manages the version of each installed JRE uniquely; therefore all JREs are usable by default. When there are multiple JRE versions and some of the versions are the same as or later than the version required for a Java application, JWS determines which version to use. For this reason, you must set up JWS so that it uses the correct JRE version to execute Java applications. The setup method depends on the JWS version. The following subsections explain the setup methods for the JWS versions.
3-4-3-1 For Java Web Start 1.4.2_xx

To set up Java Web Start 1.4.2_xx: 1. Start the Java Web Start Application Manager. 2. Select the File menu, and select Preferences. 3. In the Java Web StartPreferences window, click the Java tab. 4. Click the Find button. 5. Click the Next button. 6. Specify the installation directory of the required JRE version and then click the Next button. A dialog box appears, notifying you that the JRE is found. 7. Click the Next button to return to the Preferences dialog box. Make sure that the required version is added in the Java Runtime Versions list. 8. In the Java Runtime Versions list, select the Enabled check box for the required version, and clear the check boxes for other versions. For details about the version of JRE and JWS required for web client, see the explanation about the Java execution environment in section 3-1 . 9. Click the OK button to save your changes and exit the Java Web Start Application Manager.
3-4-3-2 For Java Web Start 5.0 and 6.0

To set up Java Web Start 5.0 or 6.0: 1. Start the Java Control Panel. 2. In the Java tab window, in Java Application Runtime Settings, click the View button. The JNLP Runtime Settings dialog box opens. 3. In the JNLP Runtime Settings dialog box, click the User tab. 4. Click the Find button. 5. Click the Next button. 6. Specify the installation directory of the required version of JRE and then click the Next button. A dialog box opens, notifying you that the JRE has been found. 7. Click the Next button. The JNLP Runtime Settings dialog box reopens. 8. Check that the required version has been added to the Java Runtime Versions list. 9. In the Java Runtime Versions list, select the Enabled check box for the required version, and clear the check boxes for other versions. For details about the version of JRE and JWS required for web client, see the explanation about the Java execution environment in section 3-1 . 10. Click the OK button to save your changes and exit the Java Control Panel.
48
3-5 Upgrading the Java GUI and clearing the cache

After upgrading the Device Manager server, you must complete the following tasks on the Device Manager web client:
Upgrading the Java GUI (see section 3-5-1 ) Clearing the Java Web start cache (see section 3-5-2 ) Clearing the browser cache (see section 3-5-3 )
3-5-1 Upgrading the Java GUI

Before you upgrade your Java GUI, check the versions of the JRE and JWS software required by the upgrade, and upgrade that software according to your version of the Device Manager. After upgrading the JRE and JWS software to the required version, you can start using the Java GUI. For details on the required JRE and JWS versions for the Device Manager web client, see the explanation about the Java execution environment in section 3-1 . You do not need to manually update the Java GUI each time the Java GUI is invoked; the Java Web Start software checks to ensure that the locally cached application is the latest version available from the Device Manager server. If it is not, it downloads and invokes the newer version.
3-5-2 Clearing the Java Web Start cache

If a previous version of the Java GUI is installed, you may not be able to download the latest version, even when you are upgrading the Device Manager. In this case, you must clear the cache in Java Web Start to download the latest version of the Java GUI from the Device Manager server. CAUTION: Clearing the cache clears all resources downloaded by JWS. To start applications using JWS, you must download those resources again. The Java GUI will be downloaded automatically when you log in to the Device Manager server. How the JWS cache is cleared depends on the JWS version. The following subsections explain the procedures for the different JWS versions.
3-5-2-1 For JWS 1.4.2_xx

To clear the cache in JWS 1.4.2_xx: 1. Start the Java Web Start Application Manager. 2. Select the File menu and then select Preferences. 3. In the Java Web StartPreferences window, click the Advanced tab. 4. Click the Clear Folder button to open the Clear Applications Folder window. 5. Click the Yes button. 6. Click the OK button to save your changes and exit the Java Web Start Application Manager.
3-5-2-2 For Java Web Start 5.0

To clear the cache in Java Web Start 5.0: 1. Start the Java Control Panel. 2. In the General tab, in Temporary Internet Files, click the Delete Files button. The Delete Temporary Files confirmation dialog box opens. 3. In the Delete Temporary Files confirmation dialog box, click the OK button. The Delete Temporary Files confirmation dialog box closes. 49
Installing the Device Manager web client 4. Click the OK button to save your changes, and exit the Java Control Panel.
3-5-3 Clearing the browser cache

Even after you upgrade the Device Manager server, the browser may display the old version of the Device Manager. If this happens, you must clear the cache in the browser. To clear the cache in an Internet Explorer browser: 1. From the menu bar, select Tools and then Internet Options. 2. In the Internet Options dialog box, click the General tab. 3. In Temporary Internet files, click the Delete Files button. 4. In the Delete Files dialog box, select the Delete all offline content check box and then click the OK button. 5. In the Internet Options dialog box, click the OK button. To clear the cache in the Mozilla browser: 1. From the menu bar, select Edit and then Preferences. 2. In the Category area of the Preferences dialog box, select Advanced and then Cache. 3. Click the Clear Memory Cache button. 4. Click the Clear Disk Cache button. 5. Click the OK button.
3-6 Setting up secure communication with Device Manager

When setting up a Device Manager system, you must set up security to ensure safe communication over the Internet or an intranet. With the Device Manager, you can use secure sockets layer and transport layer security (SSL/TLS) to encrypt network communications between the web client and either the Device Manager server or HBase Storage Mgmt Web Service. For details about security for the Device Manager server, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. When you use an SSL/TLS connection with the Device Manager server and the system does not recognize the certificate or authority issuing the certificate, a warning displayed when you start the session. This warning is also displayed for the Device Manager when you open HTML help from the following Java GUI dialog boxes:
Physical View dialog box Resource Group Administration dialog box Resource Group Properties dialog box Resource Group Allocation dialog box Change Resource Group dialog box
To suppress the warning, import the certificate into your browser following the instructions displayed in the appropriate dialog box. When you use Internet Explorer as a web browser and specify SSL on the Device Manager server, the Java GUI may not open because of an error occurring during the Java GUI download. If this problem occurs, open the Internet Options dialog box and then disable the Do not save encrypted pages to disk setting option. For details, see the Microsoft Support web site. If the web client is used on one of the following OSs and is connected to a Device Manager server by using SSL, an attempt to start the Java GUI will open the dialog box used for saving the JNLP file, but the Java GUI cannot be started.
Windows Server 2003, Standard Edition Service Pack 1 50
Windows Server 2003, Enterprise Edition Service Pack 1 Windows Server 2003, Datacenter Edition Service Pack 1 Windows Server 2003 R2, Enterprise Edition Service Pack 1
In this case, save the JNLP file in the desired location in accordance with the message displayed in the dialog box and then execute the saved file. You must perform this operation each time you start the Java GUI.
51

This chapter describes the preparation required before using the Device Manager and provides instructions for starting Device Manager operations:
Preparing to start Device Manager operations (see section 4-1 ) Link-and-launch installation requirements (see section 4-2 ) Copy pair requirements (see section 4-3 ) Starting Device Manager operations (see section 4-4 ) Linking with XP External Storage Software (see section 4-5 ) Using XP Disk/Cache Partition (see section 4-6 )
4-1 Preparing to start Device Manager operations

This section provides notes on using Device Manager to manage storage subsystems, and explains the tasks that must be performed before you can start Device Manager operations. The topics covered are as follows:
Notes on managing storage subsystems (see section 4-1-1 ) Tasks that must be performed before Device Manager operations can be started (see section 4-1-2 )
4-1-1 Using Device Manager to manage storage subsystems

The Device Manager server requires exclusive access to a storage subsystem. You must make sure that a single storage subsystem is always managed by a single Device Manager server. Do not build a system configuration where multiple Device Manager servers might be able to manage the same storage subsystem. If Device Manager and another management tool (such as XP Remote Web Console) modify the storage subsystem configuration at the same time, the operation(s) might not be performed correctly. Before using Device Manager web client (or CLI) to modify the configuration of a storage subsystem, make sure that the storage subsystem is not being accessed by any other management tool. The StorageWorks XP Disk Array SVP must be in the View mode (and not in the Modify mode). In an environment using the storage logical partition function, you can use different Device Manager servers to manage individual SLPRs, in addition to a Device Manager server that manages the entire storage subsystem. However, do not set up a system in a configuration in which multiple Device Manager servers manage the entire storage subsystem. A single Device Manager cannot manage multiple SLPRs of the same storage subsystem.
4-1-2 Tasks required before starting Device Manager operations

Before starting Device Manager operations, take the following action: 1. Make sure that the Device Manager server is installed, configured, and fully operational. For more information, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. 2. Write down the IP address of the Device Manager server.
52
Preparing for and starting operations 3. Be sure to read the release notes for HP StorageWorks XP Command View Advanced Edition software. 4. Register the license key of the storage subsystem you want to manage in Device Manager and write down the license key or obtain the license key file. 5. Verify the web client environment, making sure that the JRE and JWS software have been installed and configured properly on the web client system as described in Chapter 3. 6. Verify the configurations of the storage subsystems, making sure that the storage subsystems are configured for Device Manager operations as specified in the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. 7. Write down the IP address of each storage subsystem that you want to manage using the Device Manager. You will need the IP address to add the storage subsystem to Device Manager. 8. Run the Device Manager agent after installing the Device Manager server so that the web client can automatically recognize the hosts on which Device Manager agent is installed. For more information, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide. NOTE: Device Manager recognizes NAS-attached hosts.
9. For each host that does not have a Device Manager agent installed, write down the port WWNs. You will need this information when you add the hosts manually to Device Manager. 10. If you want to view the information about a mainframe volume (VOLSER and DEVN) from web client, install mainframe agent on a mainframe host and complete the settings for linkage with Device Manager. For details on how to configure these settings, see the manual for mainframe agent. NOTE: You cannot perform operations for a mainframe host from the web client. Although you can view the mainframe volume information that is acquired from mainframe agent, in the web client, you cannot view information about a mainframe host.
4-2 Link-and-launch Installation requirements

This section describes the requirements for performing link-and-launch operations for applications, and explains how to specify the settings for using Mozilla as a web browser.
Requirements for performing link-and-launch operations for applications (see section 4-2-1 ) Settings for using Mozilla (see section 4-2-2 )
4-2-1 Application-specific requirements

Before performing link-and-launch operations, make sure that the following link-and-launch requirements have been satisfied. For the latest information about operating systems and browsers supported by an application started from a link-and-launch operation, refer to the manuals for the application. HDLM requirements HDLM and the Device Manager agent must be installed on the management-target host of the Device Manager. See the HDLM manuals. XP Provisioning Manager software requirements The Device Manager server and XP Provisioning Manager software must be installed on the same machine.
53
Preparing for and starting operations XP Replication Monitor software requirements The Device Manager server and XP Replication Monitor software must be installed on the same machine. XP Tiered Storage Manager software requirements The Device Manager server and XP Tiered Storage Manager software must be installed on the same machine. HP Storage Essentials requirements You must specify settings for the linkage with HP Storage Essentials. For details about the settings for linking with HP Storage Essentials, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. XP Remote Web Console requirements XP Remote Web Console must be installed on the XP1024/XP128 that is being managed by the Device Manager. XP Remote Web Console functions such as XP Cache Residency Manager or XP Continuous Access Software must be installed and enabled on the storage subsystem. The Device Manager displays only functions that are installed and enabled. When using Mozilla to start XP Remote Web Console in a Solaris or HP-UX environment, you must configure the browsers and Java plug-ins. For details on how to set up the Java plug-in, see section 4-2-2 . NOTE: When using an early version of XP Remote Web Console, be aware of the following restrictions for XP12000/XP10000/SVS200 with DKC Microcode earlier than 50-04-00, and XP1024/XP128 with DKC Microcode SVP version earlier than 21-14-00: Failure status is not displayed. Version information is displayed.
NAS Manager Requirements The XP12000/XP10000/SVS200 or XP1024/XP128 managed by Device Manager must contain a NAS-CHA in which NAS Manager must be installed. Third-party software application requirements If the third-party software applies to a specific array, the Device Manager enables the link and launch of a URL from the Physical View dialog box or Show Propertiessubsystem-name subwindow for each storage subsystem. For details, see the HP StorageWorks XP Command View Advanced Edition software Device Manager CLI user guide. Specifically see the AddURLLink, GetURLLink, and DeleteURLLink API commands.
4-2-2 Settings for using Mozilla

This section explains the settings for using Mozilla to start XP Remote Web Console. NOTE: You do not need to specify the following settings when you use XP Remote Web Console as Physical View in XP24000/XP20000 or XP12000/XP10000/SVS200.
4-2-2-1 Specifying the Mozilla program that you want to use for XP Remote Web Console
To use Mozilla to start XP Remote Web Console, you must create a shell script that specifies the Mozilla program to be used. 54
Preparing for and starting operations To create a shell script that specifies the Mozilla program to be used: 1. Create a shell script named netscapeforSN, and code the following as appropriate for your environment: #!/usr/bin/sh LD_LIBRARY_PATH= path-to-Mozilla-supported-by-Remote-Web-Console $* (Enter a single space after LD_LIBRARY_PATH=.) 2. Specify the execution permissions for the shell script netscapeforSN. 3. Modify the environment variable PATH so that the shell script netscapeforSN can be executed from the command line.
4-2-2-2 Setting up the Mozilla plug-in.

To use Mozilla to start XP Remote Web Console, you must create a symbolic link to the Java plugin file in the Mozilla plugins directory. The following is an example of using Mozilla in HP-UX: # cd path-to-Mozilla-supported-by-Remote-Web-Console/plugins # ln -s /opt/java1.4/jre/plugin/PA_RISC/ns600/libjavaplugin_oji.sl. After the setup finishes, restart the browser. For details on the Java plug-in, refer to the Sun Microsystems web site.
4-3 Copy pair requirements

For details on the Device Manager server requirements, host requirements, and storage subsystem requirements for copy pair operations, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. This section describes the requirements for creating a copy pair:
P-VOL requirements (see section 4-3-1 ) S-VOL requirements (see section 4-3-2 ) RAID level requirements (see section 4-3-3 )
4-3-1 P-VOL requirements

The requirements for a logical device to be selectable as a primary volume (SP-VOL) for a copy pair differ depending on the storage subsystem or copy type. Requirements for each storage subsystem have a higher priority than the requirements common to all storage subsystems. P-VOL requirements common to all systems Table 4-1 shows the requirements common to all storage subsystems for a logical device to be selectable as a primary volume (SP-VOL).
55
Table 4-1 Common requirements for a logical device to be selectable as a primary volume (SPVOL) Copy Type
Common condition for paired volume
Requirements The logical device must be identifiable to the Device Manager agent and must not
be mounted. To confirm this, verify that the date is updated to the last update time. Exception: If the host uses the central management method for pair management, the Device Manager agent does not need to identify the logical device.
The combination of the RAID levels must satisfy the conditions shown in Table 49. LUN security must be set up for the target host. The logical device must be in an open system and must belong to a storage
subsystem for which a command device is set up, but the command device must not be mounted.
The logical device must not be a command device or a remote command device. If the host uses the central management method for pair management, the logical
device must be a volume that belongs to the storage subsystem for the command device identified by the host that manages copy pairs. XP Continuous Access Software The primary volume must not have any secondary volumes.
P-VOL requirements for XP24000/XP20000 storage subsystems Table 4-2 shows the requirements specific to XP24000/XP20000 storage subsystems for a logical device to be selectable as a primary volume (SP-VOL). Table 4-2 Requirements for a logical device to be selectable as a primary volume (SP-VOL) for XP24000/XP20000 Copy Type
Common condition for paired volume
Requirements For an internal volume to which an external volume is mapped, the host I/O
suppression mode must be disabled.
The logical device must not be a THP pool volume.

XP Continuous Access Software* The logical device must meet the following criteria:
Must not be a P-VOL or S-VOL for XP Continuous Access Software. Must not be a P-VOL or S-VOL for XP Continuous Access Journal Software. For
XP Continuous Access Synchronous Software, an XP Continuous Access Journal Software P-VOL can be used as a P-VOL for XP Continuous Access Synchronous Software.
Must belong to the main control unit (MCU) for which the remote control unit (RCU)
is set up.
Must not be a V-VOL or data pool for XP Snapshot. If the DKC microcode version is earlier than 60-02-4x-xx/xx, the logical device must
not be a THP volume XP Business Copy Software
The logical device must not be one of the following types of volumes:
A secondary volume for an XP Business Copy Software SP-VOL A primary volume, V-VOL, or data pool for XP Snapshot
If the selected logical device is an XP Business Copy Software P-VOL, the number
of S-VOL must be fewer than 3.
If the selected logical device is an XP Business Copy Software SP-VOL, the

number of S-VOL must be fewer than 2.
56
Table 4-2 Requirements for a logical device to be selectable as a primary volume (SP-VOL) for XP24000/XP20000 Copy Type
Conditions for XP Continuous Access Journal Software
Requirements The emulation type must be OPEN-V. If the DKC microcode version is earlier than 60-02-4x-xx/xx, the logical device must
not be a THP volume.
The logical device must not be a primary or secondary volume for XP Continuous
Access Asynchronous Software.
If the selected LDEV is an S-VOL of XP Business Copy Software, the copy status
of the component pair must be Split.
The logical device must not be a V-VOL or data pool for XP Snapshot. The logical device must not be a P-VOL, S-VOL, or JNL-VOL of XP Continuous
Access Journal Software.
*
If you want to use an XP Business Copy Software S-VOL as the P-VOL for an XP Continuous Access Software copy pair, the status of the XP Business Copy Software copy pair must be Split.
P-VOL requirements for XP12000/XP10000/SVS200 storage subsystems Table 4-3 shows the requirements specific to XP12000/XP10000/SVS200 storage subsystems for a logical device to be selectable as a primary volume (SP-VOL). Table 4-3 Requirements for a logical device to be selectable as a primary volume (SP-VOL) for XP12000/XP10000/SVS200 Copy Type
Common condition for paired volume XP Continuous Access Software*
Requirements
For an internal volume to which an external volume is mapped, the host I/O suppression mode must be disabled. The logical device must meet the following criteria:
Must not be a P-VOL or S-VOL for XP Continuous Access Software. Must not be a P-VOL or S-VOL for XP Continuous Access Journal Software. For
XP Continuous Access Synchronous Software, an XP Continuous Access Journal Software P-VOL can be used as a P-VOL for XP Continuous Access Synchronous Software.
Must belong to the main control unit (MCU) for which the remote control unit (RCU)
is set up.
Must not be a V-VOL or data pool for XP Snapshot.

XP Business Copy Software
The logical device must not be one of the following types of volumes:
A secondary volume for an XP Business Copy Software SP-VOL A primary volume, V-VOL, or data pool for XP Snapshot

57
Table 4-3 Requirements for a logical device to be selectable as a primary volume (SP-VOL) for XP12000/XP10000/SVS200 Copy Type
Conditions for XP Continuous Access Journal Software
Requirements The emulation type must be OPEN-V. The logical device must not be a primary or secondary volume for XP Continuous
Access Asynchronous Software.
If the selected LDEV is an S-VOL of XP Business Copy Software, the copy status
of the component pair must be Split.
The logical device must not be a V-VOL or data pool for XP Snapshot. The logical device must not be a P-VOL, S-VOL, or JNL-VOL of XP Continuous
Access Journal Software.
*
If you want to use an XP Business Copy Software S-VOL as the P-VOL for an XP Continuous Access Software copy pair, the status of the XP Business Copy Software copy pair must be Split.
P-VOL requirements for XP1024/XP128 and XP512/XP48 storage subsystems Table 4-4 shows the requirements specific to XP1024/XP128 and XP512/XP48 storage subsystems for a logical device to be selectable as a primary volume (SP-VOL). Table 4-4 Requirements for a logical device to be selectable as a primary volume (SP-VOL) for XP1024/XP128 and XP512/XP48 Copy Type
XP Continuous Access Software
Requirements
The logical device must meet the following criteria:
Must not be a primary or secondary volume for XP Continuous Access Software. Must belong to the CU (MCU) for which the RCU is set up. The logical device must not be the secondary volume for an XP Business Copy
Software SP-VOL.
XP Business Copy Software

4-3-2 S-VOL requirements

The requirements for a logical device to be selectable as a secondary volume for a copy pair differ depending on the storage subsystem or copy type. Requirements for each storage subsystem have a higher priority than the requirements common to all storage subsystems.
58
Preparing for and starting operations S-VOL requirements common to all systems Table 4-5 shows the requirements common to all storage subsystems for a logical device to be selectable as a secondary volume. Table 4-5 Common requirements for a logical device to be selectable as a secondary volume Copy Type
Common conditions for paired volumes
Requirements The logical device must be identifiable to the Device Manager agent and must not be
mounted. To confirm this, verify that the date is updated to the last update time. Exception: If the host uses the central management method for pair management, the Device Manager agent does not need to identify the logical device.
The combination of the RAID levels must satisfy the conditions shown in Table 4-9. LUN security must be set up for the selected host. The logical device must meet the following criteria:
Must not be a command device or a remote command device. Must not be selected as a primary volume. Must have the same capacity as that of the primary volume. Must not be mounted as a file system. Must not be a primary volume or secondary volume for XP Continuous Access Software, or XP Business Copy Software. If the central management method is used for pair management, the logical device must be a volume that belongs to the storage subsystem for the command device identified by the host that manages the copy pairs.
XP Business Copy The logical device must be in the same storage subsystem as the selected primary Software volume.
S-VOL requirements for XP24000/XP20000 storage subsystems Table 4-6 shows the requirements specific to XP24000/XP20000 storage subsystems for a logical device to be selectable as a secondary volume. Table 4-6 Requirements for a logical device to be selectable as a secondary volume for XP24000/XP20000 Copy Type
Common conditions for copy pairs
Requirements The logical device must be applicable to StorageWorks XP Disk Array. The emulation type must be the same as that of the selected primary volume. For a LUSE volume, the primary volume and secondary volume must have the same
number of logical devices that make up the LUSE.
For an internal volume to which an external volume is mapped, the host I/O
suppression mode must be disabled.
The logical device must not be a THP pool volume.

The primary volume must belong to the MCU, and the secondary volume must
belong to the RCU registered in that MCU.
The logical device must not be a primary volume or secondary volume for XP
Continuous Access Journal Software. For XP Continuous Access Synchronous Software, an XP Continuous Access Journal Software primary volume can be used as a secondary volume for XP Continuous Access Synchronous Software.
The logical volume must not be a primary volume, V-VOL, or data pool for XP
Snapshot.
If the DKC microcode version is earlier than 60-02-4x-xx/xx, the logical device must
59
Table 4-6 Requirements for a logical device to be selectable as a secondary volume for XP24000/XP20000 Copy Type
XP Business Copy Software* Condition for XP Continuous Access Journal Software
Requirements The logical volume must not be a primary volume, V-VOL, or data pool for XP
Snapshot.
The emulation type must be OPEN-V. The primary volume must belong to the MCU, and the secondary volume must
If the DKC microcode version is earlier than 60-02-4x-xx/xx, the logical device must
The logical device must not be a secondary volume for XP Business Copy Software. The logical device must not be a primary or secondary volume for XP Continuous
Access Software.
The logical device must not be a V-VOL or data pool for XP Snapshot. The logical device must not be a primary, secondary, or journal volume for XP
Continuous Access Journal Software.
The logical device must not be a mainframe journal volume for Universal Replicator
for Mainframe.
*
If a volume to be used for the primary volume of XP Business Copy Software is not a THP volume, we do not recommend that you use a THP volume for the secondary volume.
S-VOL requirements for XP12000/XP10000/SVS200 storage subsystems Table 4-7 shows the requirements specific to XP12000/XP10000/SVS200 storage subsystems for a logical device to be selectable as a secondary volume. Table 4-7 Requirements for a logical device to be selectable as a secondary volume for XP12000/XP10000/SVS200 Copy Type
number of logical devices that make up the LUSE.
For an internal volume to which an external volume is mapped, the host I/O
suppression mode must be disabled. XP Continuous Access Software
The primary volume must belong to the MCU, and the secondary volume must
The logical device must not be a primary volume or secondary volume for XP
Continuous Access Journal Software. For XP Continuous Access Synchronous Software, an XP Continuous Access Journal Software primary volume can be used as a secondary volume for XP Continuous Access Synchronous Software.
Snapshot. XP Business Copy Software
Snapshot.
60
Table 4-7 Requirements for a logical device to be selectable as a secondary volume for XP12000/XP10000/SVS200 Copy Type
Condition for XP Continuous Access Journal Software
Requirements The emulation type must be OPEN-V. The primary volume must belong to the MCU, and the secondary volume must
The logical device must not be a secondary volume for XP Business Copy Software. The logical device must not be a primary or secondary volume for XP Continuous
Access Software.
The logical device must not be a V-VOL or data pool for XP Snapshot. The logical device must not be a primary, secondary, or journal volume for XP
Continuous Access Journal Software. Note that, for XP Continuous Access Journal Software (Resync), an XP Continuous Access Journal Software secondary volume can be used.
The logical device must not be a mainframe journal volume for Universal Replicator
for Mainframe.
S-VOL requirements for XP1024/XP128 and XP512/XP48 storage subsystems Table 4-8 shows the requirements specific to XP1024/XP128 and XP512/XP48 storage subsystems for a logical device to be selectable as a secondary volume. Table 4-8 Requirements for a logical device to be selectable as a secondary volume for XP1024/XP128 and XP512/XP48 Copy Type
number of logical devices that make up the LUSE. The primary volume must belong to the MCU, and the secondary volume must belong to the RCU registered in that MCU.
4-3-3 Copy pair volume requirements for RAID levels

Requirements for the RAID level of copy pair volumes differ depending on the storage subsystem or copy type. Table 4-9 shows the allowable combinations of RAID levels for copy pair volumes. Table 4-9 Combinations of RAID levels for copy pair volumes Copy Type Storage subsystem XP24000/XP20000 and XP12000/XP10000/SVS200
XP Continuous Access Software XP Business Copy Software Any combination of RAID1, RAID5 and RAID6 Any combination of RAID1, RAID5 and RAID6
XP1024/XP128 and XP512/XP48

Any combination of RAID1 and RAID5 Any combination of RAID1 and RAID5
61
Table 4-9 Combinations of RAID levels for copy pair volumes Copy Type Storage subsystem XP24000/XP20000 and XP12000/XP10000/SVS200
XP Continuous Access Journal Software Any combination of RAID1, RAID5 and RAID6
XP1024/XP128 and XP512/XP48

N/A
4-4 Starting Device Manager operations

After you have installed the Device Manager, prepared for Device Manager operations, and logged in to the Device Manager server, you are ready to start Device Manager operations. To start Device Manager operations operations and set up an efficient Device Manager environment: 1. Log in to the Device Manager with the System account (see section 5-1 ) 2. Change the password for the System account from the default password to prevent unauthorized access (see section 6-2-4 ). 3. Create users who can perform all resource operations and user management operations provided by Device Manager (see section 6-2-1 ). After you have created the users, grant them the User Management and Admin permissions and assign the All Resources resource group to the users. 4. Create the logical group hierarchy (see section 7-3 ). 5. Create a user-defined resource group, and associate it with a logical group (see section 6-3-1 ). 6. Assign the created resource group to the users (see section 6-3-2 ). This enables specific users to access specific resources. 7. Add the connected storage subsystems to the Device Manager server (see section 10-1-2 ). The volumes of the added subsystems are assigned to the All Resources resource group, and are placed on the All Storage object. CAUTION: The Device Manager server requires exclusive access to a storage subsystem. For details, see section 4-1-1 . NOTE: In an environment using the storage logical partition function, you can use different Device Manager servers to manage individual SLPRs, in addition to a Device Manager server that manages the entire storage subsystem. 8. Add the host name and WWN of each host that manages a storage to the Device Manager by installing the Device Manager agent on each host and then executing the HiScan command, or by entering the host name using the Device Manager web client (see section 9-4-2 ) or CLI. IMPORTANT: Add all hosts before performing a LUN Scan operation. If you do not enter the hosts before performing a LUN Scan, the LUN Scan will automatically create a unique host name (HOST_0, HOST_1, etc.) for each WWN. This can create a significant number of hosts depending on the size of the environment. 9. You are now ready to perform storage operations (see section 7-6 ), such as adding and moving storage, adding and deleting volume paths, configuring LUN security, and managing copy pairs.
62
Preparing for and starting operations 10. After the storage operation setup is complete, update the host information by executing the HiScan command on the Device Manager agent or by refreshing the host on the Device Manager web client. 11. Perform a LUN Scan operation on each storage subsystem if necessary. For details about the conditions required for performing a LUN Scan operation, and about how to perform the operation, see section 8-3 . 12. When you are finished performing Device Manager operations, be sure to log out to prevent unauthorized access (see section 5-1 for logout instructions).
4-5 Linking with XP External Storage Software

In an XP24000/XP20000 or XP12000/XP10000/SVS200 subsystem, volumes of another storage subsystem connected via a SAN can be handled as virtual interval volumes. This feature is called XP External Storage Software. Figure 4-1 shows an example of a system configuration using XP External Storage Software.
Figure 4-1 System configuration using XP External Storage Software
63
Preparing for and starting operations A storage subsystem connected to a storage subsystem that uses XP External Storage Software is called an external subsystem. Of the volumes that the external subsystem manages, those volumes mapped to the storage subsystem that uses XP External Storage Software are called external volumes. A storage subsystem that uses XP External Storage Software can manage external volumes as virtual internal volumes by mapping the external volumes to internal volumes of the storage subsystem. For details on XP External Storage Software, see the HP StorageWorks XP External Storage software user guide.
4-5-1 Advantages of linking with the Device Manager

In a storage subsystem that uses XP External Storage Software, the Device Manager distinguishes between internal volumes and external volumes, and displays them separately. For example:
To allocate reliable storage to a host, you can select a volume from the internal volumes. To allocate lower cost-per-bit storage for use as an S-VOL for the copy pair functionality, you can select a volume from the external volumes.
If you remove the LUN settings or LUN security settings for an external volume in an external subsystem management window, the storage subsystem that uses XP External Storage Software can no longer use the external volume. To avoid the problem, the Device Manager provides the Detailed InformationLDEV-number dialog box, which shows whether the volume is used as an external volume. To shows whether a volume in an external subsystem is an external volume, make sure that the Device Manager has already found both the storage subsystem that uses XP External Storage Software and the external subsystem.
4-5-2 Tasks required for using XP External Storage Software

To configure the settings required to use XP External Storage Software: 1. Use the Device Manager to find a storage subsystem that uses XP External Storage Software and find storage subsystems that can be used for external subsystems. 2. In a storage subsystem that uses XP External Storage Software, set the port that you want to use for the external connection as an external port. Device Manager manages the external port as a special host. For details on how to use Physical View to set a port as an external port, see the XP External Storage Software documentation. 3. Specify an external subsystem port to be connected to the external port. For details on the setting values for a port and using external volumes, see the XP External Storage Software documentation. 4. Specify an external volume in the external subsystem. Select the port specified in step 3 and add storage. For LUN security, select the external port that you set in step 2. The port will be treated as a host. For details on how to add storage, see section 7-6-2 . When external volumes are assigned to an external port this way, Device Manager can manage those volumes because the external port is treated as a special host. 5. Use Physical View of the storage subsystem that uses XP External Storage Software to map the external volumes to internal volumes. For details on mapping a volume, see the XP External Storage Software documentation.
64
Preparing for and starting operations Once the settings are configured, you can use the external volumes set in the external subsystem as well as LUs contained in XP12000/XP10000/SVS200 subsystem.
4-6 Using XP Disk/Cache Partition

In an XP24000/XP20000 or XP12000/XP10000/SVS200 storage subsystem, you can use XP Disk/Cache Partition to logically divide the resources in the storage subsystem. XP Disk/Cache Partition provides two functions, a cache logical partition function and a storage logical partition function.
4-6-1 Cache logical partition function

The cache logical partition function logically divides a cache shared in a storage subsystem into partitions. A partition of the cache is called a CLPR (Cache Logical PaRtition). By allocating a separate virtual cache to each host, you can prevent the I/O processing on a specific host from degrading the performance of other hosts. For details on the cache logical partition function, see the storage subsystem XP Disk/Cache Partition user guide. The Device Manager can display the number of the CLPRs to which the volume belongs as an LDEV attribute. You can also set up the cache logical partition function from the Physical View. For details about the Physical View, see section 10-2 .
4-6-2 Storage logical partition function

The storage logical partition function of XP Disk/Cache Partition logically divides the storage subsystem resources (such as ports, CLPRs, and LDEVs) into partitions. A partition of the resources is called an SLPR (Storage Logical PaRtition). The partitions that are called SLPR can be managed individually. An environment using the storage logical partition function has an administrator for the entire storage subsystem as well as administrators for individual SLPRs. An administrator for a SLPR is called a partitioned storage administrator. Figure 4-2 shows an example of managing the partitioned resources using the storage logical partition function.
65
Figure 4-2 Using the storage logical partition function For details, refer to the XP Disk/Cache Partition user guide. If you use a partitioned storage administrator's user ID when you add a storage subsystem to the Device Manager, only the resources that belong to the SLPR that the partitioned storage administrator is managing can be accessed from the Device Manager. In this configuration, Device Manager APIs, such as the SMI-S provider, allow their clients to manage only the same resources. The Device Manager can manage either the entire array or a single SLPR from the array. It cannot manage multiple SLPRs from one array. The Device Manager can display the number of the SLPR to which the volume belongs as an LDEV attribute. The storage logical partition function can be set up from the Physical View. For details about using the Physical View, see section 10-2 . For a storage subsystem that has been added by a user ID that has partitioned storage administrator permission, operations for managing copy pairs cannot be performed. Also, copy pair information will not be displayed for the LDEV attribute. For a storage subsystem that has been added by a user ID that has partitioned storage administrator permission, operations for managing THP pools cannot be performed.
66

This chapter describes Device Manager system operations. These include:
Logging in and out of Device Manager (see section 5-1 ) Using the Device Manager main window (see section 5-2 ) Viewing and installing license information (see section 5-3 ) Performing alert operations (see section 5-4 ) Viewing the task list (see section 5-5 ) Launching other applications from the Device Manager (see section 5-6 ) Downloading Device Manager software (see section 5-7 )
5-1 Logging in and out of the Device Manager

5-1-1 Logging in to the Device Manager
To use the Device Manager, you must log in as a user who has been granted one or more Device Manager permissions and been assigned a resource that is managed by the Device Manager. When you log in to Device Manager for the first time, use the System account common to the XP Command View AE Suite. For details about the System account , see section 2-1-3 . NOTE: When the OS is Windows XP (Service Pack 2) or Windows Vista in which the Classic Start Menu is enabled, if you use web client running Internet Explorer 7.0, start Internet Explorer 7.0 from the Start menu. If you start Internet Explorer 7.0 from the desktop icon, you cannot use the Java GUI to start an application that uses the web browser. NOTE: If you use Internet Explorer 6.0 as a web browser in an IPv6 environment, you cannot access Device Manager even if you specify an IPv6 address for the IP address of the Device Manager server. When you use Internet Explorer 6.0 to establish IPv6 connections, specify the IPv6 address and host name of the Device Manager server in the hosts file, and then use the host name to access Device Manager. To log in to Device Manager: 1. Launch the web browser, and enter the URL for the Device Manager server: http://Device-Manager-server-address:port-number/DeviceManager/ where: Device-Manager-server-address = The IP address or host name of the Device Manager server; for example, "localhost" port-number = enter the port number of the HBase Storage Mgmt Web Service (default = 23015) The Device Manager Login window opens.
67
NOTE: For SSL, use https and port 23016 (default). For details on port numbers, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. The Device-Manager-server-address and port-number values are defined during installation of the Device Manager server. For details, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. IMPORTANT: If desired, you can set a warning banner message to display in the Login window. For details on how to configure the setting, see section 6-4-3 . 2. If you are accessing Device Manager for the first time after installation, a message asking you to enter the license key appears. In this case, install the Device Manager license key and then log in. For details on registering the license key, see section 5-3 . 3. In the Device Manager Login window, enter your User ID and Password and then select Login (Remember that the password is case sensitive). 4. The Device Manager main window opens (see section 5-2 ). This window provides access to all Device Manager functions. See section 4-4 for instructions for starting Device Manager operations. IMPORTANT: A user account might be locked after repeated failures to log in. If this happens, ask a user who has the User Management permission to unlock the user account. You cannot log in to Device Manager until the user account is unlocked. IMPORTANT: For Device Manager to work properly, the Device Manager server must be the same version as the Java GUI. Check the versions by performing the following procedures: To check the Device Manager server version, select Help and then About in the global tasks bar area
on the Device Manager main window.
To check the Java GUI version in the web client, select About in the menu bar on the Physical View for
XP1024/XP128 or XP512/XP48, or click the About button on the resource group administration window.
If the Java GUI is an earlier version than the Device Manager server, clear the Java Web Start (JWS) cache (see section 3-5-2 ) and then re-install the Java GUI.
5-1-2 Logging out of Device Manager

To prevent unauthorized use of Device Manager, each user must log out of the Device Manager when finished. The Device Manager maintains an audit log of all user actions to enable verification and traceability of its operations. CAUTION: When you log out of the Device Manager, you are also logged out of other XP Command View AE Suite and the Java GUI. If you log out of Device Manager before the tasks you executed in the Java GUI are completed, the processing may be canceled and inconsistencies may occur in the system. Finish all the tasks and then log out from Device Manager. To log out of the Device Manager: 1. In the global tasks bar area of the Device Manager main window, select File and then Logout, or click the Logout button. 2. When the confirmation window appears, click the OK button to log out, or click the Cancel button to cancel your request to log out of Device Manager.
5-2 Using the Device Manager main window

Observe the following recommendations when using the Device Manager main window:
68
Make sure that the window has finished reloading before performing any operations. An operation might be possible while reloading a window, depending on the number of window items or network status. In such a case, make sure that the window has finished reloading before performing the operation. If the operation is performed during the reload, an error can occur. If you close the window that is showing the progress of an operation during an update, information indicating the success or failure of the update operation is not displayed. If you press the Esc key while the Device Manager is processing you cannot use the Device Manager. To remedy the situation, click Refresh Tree in the navigation area or press the F5 key to refresh the screen. If a pop-up window is open, close and then reopen it. If you open a dialog box while performing an operation in the main window, the dialog box locks if you do not take further action within 60 minutes. If this occurs, close and reopen the dialog box and then perform the operation from the beginning. Use the links and buttons provided in the Device Manager main window to perform GUI operations. Do not use web browser functions, such as Reload or Back. These functions may display unexpected window. For example, if you are using Internet Explorer as your web browser, right-clicking a link in the Device Manager's application area and selecting Open in the pop-up window produces a blank window. If you have been using browser functions, click Refresh Tree in the navigation area, or press the F5 key to refresh the screen. If a dialog box is open, close and reopen it.
For information on the Device Manager warning messages, see section 12-3 . If you change the language environment of the web browser while using web client, click the Refresh Tree button in the navigation area before performing the next operation. If you are using JRE 6.0 in Solaris 10, the main window is displayed in front of the Java GUI after operations executed on the Java GUI have been completed.
The Device Manager main window (see Figure 5-1) allows you to access all Device Manager functions. To open the main window, open the web browser, and log in to the Device Manager.
Figure 5-1 Device Manager main window components The Device Manager main window is divided into the following sections:
69
Global tasks bar area (see section 5-2-1 ) Explorer menu (see section 5-2-2 ) Dashboard menu (see section 5-2-3 ) Application bar area (see section 5-2-4 ) Navigation area (see section 5-2-5 ) Application area (see section 5-2-6 ) Dialog box (see section 5-2-7 )
5-2-1 Global tasks bar area

The global tasks bar area in the Device Manager main window (see Figure 5-1) enables the loggedin user to perform basic operations, such as logging out and displaying version information. This area also displays information about the user who is currently logged in. The following functions are available in the global tasks bar area:
File menu
Close: Closes the web browser. Logout: Enables you to log out of Device Manager and other active XP Command View AE
Suite, and closes the web browser.
Go menu
Download: Displays the Device Manager software deployment dialog box. For details on
the dialog box, see section 5-7 .
Links: Displays the Link dialog box, from which you can start user-registered applications. If
an application is not registered, this submenu is not displayed.
Help menu
Online Manual: Displays the GUI Help for the Device Manager. GUI Help describes the
items in Device Manager windows.
Documentation Home Page: Displays HP's web site for the online manual. About: Displays the Device Manager version and license information, and enables you to
enter your license key when required.
Logged in as: field Displays the full name of the logged-in user. When the full name is unavailable, the user ID is displayed. Close button Closes the web browser. Logout button Enables you to log out of the Device Manager and other active XP Command View AE Suite, and closes the web browser.
5-2-2 Explorer menu

The Explorer menu in the Device Manager main window (see Figure 5-1) enables the logged-in user to select an operation available in the Device Manager. When you choose a menu option, information in the application bar area, navigation area, and application area changes according to the selected option. You can set the area that contains the Explorer and Dashboard menus to show or be hidden by clicking the leftmost button in the global tasks bar area. The Explorer menu displays the following items:
Resources: A submenu used to access and operate Device Manager resources. 70
All Storage or My Storage: If you are assigned to the All Resources resource group, All
Storage is displayed. If you are assigned to a user-defined resource group, My Storage is displayed. All Storage or My Storage menu items enable you to manage storage that is accessible to you (see Chapter 8).
Hosts: Enables you to perform operations related to host management (see Chapter 9). Subsystems: Enables you to perform operations for storage subsystems that are managed
by the Device Manager. This menu item is displayed only if you are assigned to the to the All Resources resource group (see Chapter 10).
My Groups: A menu for accessing and operating logical groups that are available to you.
Logical Groups: Enables you to perform operations logical groups (see Chapter 7).
Administration : Allows you to access and operate user accounts and resource groups (see Chapter 6).
Users and Permissions: Enables a user logged in with User Management permission to
perform operations on user accounts. This menu item is displayed only if you are logged in with User Management permission.
Resource Groups: Enables a user logged in with Admin permission to perform operations
on resource groups. This menu item is displayed only if you are logged in with Admin permission.
Security: Enables operations for security options setup to be performed. This menu item
is displayed only if you are logged in with User Management permission.
Tasks: Enables you to view task information (see section 5-5 ). Alerts: Enables you to perform operations on alerts (see section 5-4 ). This menu item is displayed only if you are assigned to the All Resources resource group. Reports: Enables operations for reports (see Chapter 11). This menu item is displayed only if you are assigned to the All Resources resource group. Settings:
User Profile: Enables you to view and edit of the profile of the logged-in user (see Chapter
6).
License Info: Enables you to view version and license information and to set license (see
section 5-3 ).
5-2-3 Dashboard menu

The dashboard menu in the Device Manager main window (see Figure 5-1) displays all XP Command View AE Suite, whether installed or not. The products that are installed are enabled; the products that are not installed are disabled (dimmed). To start an enabled product, click the GO button (If a product is already started the GO button is not displayed). To show or hide the area that contains the Explorer and Dashboard menus, click the leftmost button in the global tasks bar area. Table 5-1 shows the XP Command View AE Suite names and their corresponding dashboard menu items.
71
Table 5-1 Product names and corresponding dashboard menu items Product name
Device Manager XP Provisioning Manager software XP Replication Monitor software XP Tiered Storage Manager software Storage Essentials
Dashboard item
DevMgr ProvMgr RepMon TSMgr DLMgr
5-2-4 Application bar area

Displays the menu item selected in the Explorer menu. If there are operations that can be performed for the object selected in the navigation area, the buttons for the operations are also displayed. The Help button is displayed in the application bar area. Clicking the Help button displays a GUI Help for the subwindow that is displayed in the application area. GUI Help explains items displayed in the Device Manager windows.
5-2-5 Navigation area

The navigation area of the Device Manager main window (see Figure 5-1) displays the object tree appropriate for the item selected in the Explorer menu. The target object can be selected from this tree. When an object is selected in the navigation area, the application area displays the information for the selected object. The navigation area is displayed only when the selected operation target is in a tree structure. To show or hide the navigation area, click the leftmost button on the application bar area. When you click the Refresh Tree button in the navigation area, all information displayed in the navigation area and the application area of the main window is refreshed. IMPORTANT: The information on the Device Manager main window is not automatically updated. After you perform a
Device Manager operation, click the Refresh Tree button to display the latest information.
When using Mozilla 1.4, if you attempt to display another window while updating information, the result
of the update is not applied to the object tree in the navigation area. For example, if you display a list of storage subsystems while a host is being added, the added host is not displayed in the tree for hosts in the navigation area. In this case, click the Refresh Tree button to display the latest information.
5-2-6 Application area

The application area in the Device Manager main window (see Figure 5-1) displays details about the object selected in the navigation area and provides buttons for performing operations. The display area in the application area is called a subwindow. The subwindow name is displayed at the top of the application area. When an object is selected in the navigation area, the application area also displays the location of the object in the object tree managed by Device Manager. The location is displayed using greaterthan signs (>) to separate the objects from the menu item selected in the Explorer menu down to the selected object. For example, when host_0 is selected in the navigation area, the location displayed in the application area is as follows: Hosts > host_0
72
Performing Device Manager system operations When you click an object in the displayed location, the appropriate information for the object you clicked is displayed in the application area. Capacity indication rules: Unless otherwise noted, the following rules apply to the calculation method and the format of the displayed capacity:
The capacity is calculated in KB. The unit of the capacity to be displayed changes depending on the capacity. If the capacity is smaller than 1GB, the capacity is displayed in MB. If the capacity is 1GB or larger, but less than 1TB, the capacity is displayed in GB. If the capacity is 1TB or larger, the capacity is displayed in TB. When the capacity is displayed in MB, only the integer part is displayed. When the capacity is displayed in GB or TB, the capacity is truncated to two decimal places.
5-2-7 Dialog box

A dialog box is a pop-up window that is displayed when an operation button, a link in the application bar area, or the application area is clicked. A dialog box displays the details of the selected operation, allowing you to set the necessary conditions for the operation and then to perform the operation. The following items are displayed in all dialog boxes:
Title: Indicates the name of the dialog box. Help: When selected, displays GUI Help, which describes the items displayed in the dialog box.
5-2-8 Sortable table

The Device Manager often lists objects in the application area or a dialog box in a sortable table format. The sortable table allows you to set Pagination, Sort, Select All, and/or Selecting a Range functions (see Figure 5-2). The functions available differ depending on the material included in the table. In the Device Manager, sortable tables are available in the following application areas and dialog box:
Figure 5-2 Sortable table
73
NOTE: If any of the following conditions exist, sortable table operations might take time because many array groups are created in a storage subsystem. There are many externally connected LDEVs. There are many V-VOLs of XP Snapshot. There are many THP-VOLs of XP24000/XP20000. In the above cases, the following problems might occur depending on the browser you are using. When using Internet Explorer:
Switching pages or changing the number of lines to be displayed might take time.
When using Mozilla:

When displaying a sortable table, a message might be displayed that indicates the processing is taking a long time.
5-2-8-1 Pagination function

The pagination function is used to list objects in a page format and allows you to select the number of lines per page. You can perform the following operations using the pagination function:
Select the number of lines to be displayed on one page: You can select, from a drop-down list the number of lines to be displayed on one page. You can also set the line count options in the server properties file. The default options are 25 and 300 (lines). When a sortable table is displayed for the first time or redisplayed, the smaller value is applied as the number of lines to be displayed on one page, regardless of which option you had previously chosen. Therefore, if you change the value of the options in the server properties file, specify as the smaller value the number of lines that you want to initially display on one page. The maximum number of lines that can be displayed in a sortable table depends on the web browser and the environment. The maximum value that can be set as the number of display lines is shown below for each web browser:
Internet Explorer 7.0 and Internet Explorer 6.0: 1,000 (lines) Mozilla 1.4: 2,000 (lines) Mozilla 1.7: 300 (lines)
For details on how to set the line count options, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
Navigate pages: You can navigate to the first page, the previous page, the next page, or the last page. Display the current page number: You can display the total number of pages and the number of the current page. Jump to a specific page: You can jump to a specific page by entering the page number in a text box, and pressing the Enter key.
When you execute the Sort function, the display always returns to the first page.
5-2-8-2 Sort function

When you click the title of a column in a sortable table, the entire table is sorted on that column. When the table has been sorted, an icon indicating whether the sorting is in ascending or descending order appears to the right of the column title.
5-2-8-3 Select all function

If you select the check box in the title line, the check boxes for all items on the displayed page are selected. Alternatively, if you select the check boxes for all items on the displayed page, the check box in the title line is selected. Clearing the check boxes of the title line or all of the items on the displayed page clears all.
74
5-2-8-4 Selecting a range function

To select (or deselect) a range of rows, select the check box of the row that starts the range, hold down the Shift key, and select (or deselect) the check box of the row that ends the range. The check boxes of the rows between the start and end rows of the range are automatically selected (or deselected).
5-2-9 Filtering function

The filtering function enables you to extract the objects that match the conditions selected from the list of objects displayed in the sortable table. The filtering function can be used in conjunction with the sort function. Uses of the filtering function When the filtering function is available in the sortable table, the Filter and Filter Off buttons are displayed. When you click the Filter button, the Filterobject-name dialog box appears (see Figure 5-3). Use this dialog box to specify filtering conditions and perform filtering.
Figure 5-3 Filter dialog box Filtering methods The filtering methods available depend on the items selected for the filtering conditions:
Range specification: Objects within the specified range are extracted. Use the >, <, >=, <=, and = operators to specify a condition range. Exact match specification: Only objects that exactly match the specified condition are extracted. Select either of the operators is or = to specify the condition. Partial match specification: Objects that include the specified text character string are extracted. Select contains as the condition operator.
If no objects matching the conditions are found, only the title line is displayed. Using the filtering function: To use the filtering function: 1. In the sortable table in the application area, click the Filter button.
75
Performing Device Manager system operations The Filterobject-name dialog box appears. 2. Specify the filtering conditions.
From the drop-down list, select a filtering method to be used when multiple conditions are
set. All uses the AND condition for filtering. Any uses the OR condition for filtering. When OR is used for filtering, you can set multiple conditions. For the number of conditions that can be set when AND is used for filtering, see Table 5-2.
Attribute: From the drop-down list, select the attribute you want to set as a filtering
condition.
The drop-down list for operators contains operand(s) that correspond to the selected
Attribute.
Value text box: In the text box, directly enter a filtering condition appropriate for the item
selected from the Attribute drop-down list. Alternatively, select the filtering condition from the drop-down list. Table 5-2 lists and describes the combinations of attributes and operators that can be specified as filtering conditions, the values that can be specified, and the number of conditions that can be set when the AND condition is used for filtering. Table 5-2 Filtering conditions Attribute Operator Value Number of conditions when AND is used for filtering
If the combination of operators consists of <= and >=, a maximum of 2 conditions can be specified.
LDEV
<=, >=, =
Specify a condition in the same format as the format displayed in the LDEV list. If the list contains LDEVs in different formats, only the LDEVs in the specified format are extracted. You cannot specify LDEVs in different display formats at the same time. If the upper limit is omitted, the maximum value is assumed; if the lower limit value is omitted, the minimum value is assumed. Enter a value for the operator being used as described below:
When using >=

Enter the minimum LDEV number to be extracted. If the value is omitted, the minimum value is assumed.
When using <=

Enter the maximum LDEV number to be extracted. If the value is omitted, the maximum value is assumed.
When using =
Enter only one LDEV number to be extracted or two separated by a hyphen (-). If you enter two numbers, all the LDEVs in the range of these two numbers are matched. Type contains Select from the drop-down list. Specifies a character string that is or forms part of an array group. Enter from 1 to 20 characters. Select from the drop-down list. Select from the drop-down list. One condition can be specified. One condition can be specified. One condition can be specified. One condition can be specified.
ArrayGroup is, contains Port Port Type is is
76
Table 5-2 Filtering conditions Attribute Operator Value Number of conditions when AND is used for filtering
Host
contains
Specify the character string included in the host One condition can be name (which is not case sensitive). If you enter specified. n/a or nothing, data whose host name is n/a or no data is extracted. The WWN is not subject to filtering. Select from the drop-down list. If you select (blank), blank columns are extracted. The number of LDEVs displayed for the LUSE volume is not subject to filtering. Select the units from the drop-down list and then enter the capacity by using single-byte numeric characters. You can enter a maximum of 9 digits for the capacity.If nothing is entered, an error occurs. To specify a range, enter the following value: One condition can be specified.
EMU Type
is
Capacity#
<, >, <=, >=, =
Multiple conditions can be specified.
When using > or >=

Enter the minimum capacity of LDEV to be extracted.
When using < or <=

Enter the maximum capacity of LDEV to be extracted. Consumed Capacity# <, >, <=, >=, = Enter one of the following: enter the capacity in single-byte numeric characters. A maximum of 9 digits can be specified. Multiple conditions can be
Select a unit from the drop-down list, and then specified.
Enter the character string n/a (not case

sensitive). When you enter n/a, select the operator =. If you make no entry at all, an error results. To specify a range, enter the following value:
When using > or >=

Enter the minimum capacity of LDEV to be extracted.
When using < or <=

Enter the maximum capacity of LDEV to be extracted. Current Controller Pool ID is is Select from a drop-down list. Select from a drop-down list. Select from the drop-down list. Select from the drop-down list. Select from the drop-down list. One condition can be specified. One condition can be specified. One condition can be specified. One condition can be specified. One condition can be specified.
Subsystem is Logical Group Volume Attr is contains
77
Table 5-2 Filtering conditions Attribute Operator Value Number of conditions when AND is used for filtering
One condition can be specified. One condition can be specified. One condition can be specified. One condition can be specified.
Copy Type Copy Role Copy Status
contains contains contains
Select from the drop-down list. Select from the drop-down list. Select from the drop-down list. Select from the drop-down list. If you select (blank), blank columns are extracted.
is External Subsystem
# The value displayed in Capacity is rounded down from the actual capacity. As a result, the value that is shown might be less than the actual capacity. When filtering is executed, the actual value is used as the extraction condition. Therefore, even though the displayed value matches the condition, it might not be extracted. For example, a volume of 1.001GB is displayed as 1.00GB. If you specify =1 GB as the filtering condition, 1.001 GB would not be extracted. For details about displaying capacity, see section 5-2-6 . 3. To specify multiple conditions, click the + (plus) button to add a new condition line. To delete a condition, click the (minus) button on the right of the condition line. When you click the Reset button, the changes to the conditions are discarded and the settings are reset to those in effect when the Filterobject-name dialog box was opened. 4. Click the Apply or OK button to apply the filters. When you click the Apply button, the filtering is performed. When filtering is done, the Filterobject-name dialog box is displayed again. This feature allows you to easily view the objects under a series of filtering conditions. The filtering conditions are enabled until one of the following operations is performed:
Clicking the Filter Off button for the sortable table. Moving from the subwindow the sortable table is in to another subwindow. Closing the window the sortable is in.
5-3 Viewing and installing license information

The License dialog box is used to register your Device Manager license key. The dialog box (see Figure 5-4) displays the following information:
Version License type The license types are Permanent, Temporary, Emergency, and Unregistered. Serial number of the storage subsystem associated with the license key Licensed capacity Displays the licensed capacity. If you are using the Core CLI/SMI-S license, Core CLI/SMI-S is displayed.
IMPORTANT: When a temporary license is used, the serial number of the storage subsystem and the license capacity that correspond to the license key are not displayed.
78
Figure 5-4 Device Manager License Information dialog box NOTE: You cannot install the license key of a different XP Command View AE Suite in the dialog box for Device Manager license information. To install the license key of a different XP Command View AE Suite, install the license key in the dialog box for that product's license information. If you start an XP Command View AE Suite whose license key has not been installed from the Dashboard menu, that product's user login dialog box will be displayed.
To view Device Manager license information or install a license key: 1. Open the dialog box for Device Manager license information and perform one of the following procedures:
Before you have logged in to Device Manager, click the License button on the Device
Manager login window.
After you have logged in to Device Manager, in the global tasks bar area, select Help and
then About.
After you have logged in to Device Manager, in the Explorer menu, select Settings and
then License Info. To install a license key, in the License Info subwindow, click the Edit License button. If you only want to view license information, go to step 4. 2. Enter the license key.
To enter the license key directly, select the Key radio button and then enter the license
key.
To use a license key file, select the File radio button, and use the Browse button to
select a license key file. 3. To install the license key entered in step 2, click the Save button. A message appears, stating that the license key has been installed. 4. Click the Close button.
79
5-4 Performing alert operations

The Device Manager provides functionality for alerts on storage subsystems. This functionality is accessible only to users assigned to the All Resources resource group. Device Manager alert operations include:
Viewing alerts (see section 5-4-1 ) Monitoring alerts (see section 5-4-2 ) Deleting alerts (see section 5-4-3 )
The Alerts option in the Explorer menu provides access to the alert operations. When you select the Alerts option, the application bar area displays the Monitor Alerts button, and the application area displays the Alerts subwindow (see Figure 5-5).
Figure 5-5 List ObjectsAlerts subwindow
5-4-1 Viewing alerts

Use the Device Manager to view a list of all alerts for all storage subsystems or a selected storage subsystem, and detailed information about a specific alert. These functions can be executed only by users who are assigned All Resources as a resource group. Note that these functions are not accessible to users assigned a user-defined resource group.
5-4-1-1 Viewing all alerts for all storage subsystems

To view alerts for all storage subsystems and the detailed information about a specific alert: 1. In the Explorer menu, select Alerts. The Alerts subwindow appears in the application area (see Figure 5-5). The subwindow lists a maximum of 100 alerts for all storage subsystems in reverse chronological order. 2. In the Alerts subwindow, click the description link for an alert for which you want to view more detailed information. The Detailed InformationAlert dialog box displays the following information for the selected alert:
Number: Serial number assigned to the alert by the Device Manager server Type: Type of alert: Server (alert detected by server polling), or Trap (alert reported
from the device) 80
Source: Name and IP address (subsystem-name@IP-address) of the storage subsystem

where the alert originated.
Severity: Code defining the severity of the alert.

The following shows the codes displayed and their meanings: Table 5-3 Alert severity codes Code
0 1 2 3 4 5
Meaning
The severity of the error is unclear. No error has occurred. The storage subsystem has completely stopped. The part where an error has occurred is not working. A partial error has occurred. A slight error has occurred.
Component: Component where the alert is located. Description: Details about what triggered the alert Action To Take: Recommendation for how to handle the alert Data: Data used to analyze the alert If the alert type is Server, a message that shows the contents of the alert is displayed. If the alert type is Trap, the SIM data is displayed.
Time Of Alert: Date (yyyy/mm/dd) and time (hh:mm:ss) when the alert occurred.
IMPORTANT: If you remove a storage subsystem for which an alert has occurred and then attempt to display the alert information for the removed storage subsystem, ARRAY.storagesubsystem-type (for example, ARRAY.XP10000) is displayed in Source. If this happens, either delete the alert information if it is not needed, or add the storage subsystem to Device Manager again.
5-4-1-2 Viewing alerts for a selected storage subsystem

To view a list of alerts for a selected storage subsystem and detailed information about a specific alert: 1. Display the storage subsystem properties (see section 10-1-3 ). The subsystem-name subwindow is displayed in the application area. If there are alerts for the selected storage subsystem, according to the number of alerts, red lines will be displayed in the Alerts indicator of the subwindow. 2. Click the Alerts indicator. The List ObjectsAlerts dialog box, which displays a list of alerts occurring in the storage subsystem, appears. 3. In the List ObjectsAlerts dialog box, click the description link for an alert for which you want to view more detailed information. The Detailed InformationAlert dialog box appears and displays the detailed information about the selected alert. For details on the displayed information, see section 5-4-1-1 .
5-4-2 Monitoring alerts

A user assigned to the All Resources resource group can use the Device Manager to monitor storage subsystem alerts and view information about alerts in real-time.
81
Performing Device Manager system operations To monitor alerts as they occur and view information about them: 1. From the Explorer menu, select Alerts. 2. Click the Monitor Alerts button in the application bar area to open the MonitorAlerts dialog box. When an alert occurs, the MonitorAlerts dialog box notifies you and displays the time of the alert with the following message: Alerts occurred. Time date (yyyy/mm/dd/hh/mm/ss) 3. To acknowledge the alert and continue monitoring, click the Confirm button in the Monitor window. To stop monitoring alerts, click the Close button in the Monitor window. NOTE: When the Alerts subwindow or subsystem-name subwindow is displayed in the application area, and an alert occurs during monitoring, the Alert information currently displayed in those subwindows is not automatically updated. To refresh the application area, click the Refresh Tree button in the navigation area.
5-4-3 Deleting alerts

A user assigned to the All Resources resource group and granted Modify permission can delete alerts from the Device Manager server. To delete one or more alerts from the Device Manager server: 1. In the Explorer menu, select Alerts to display a list of alerts in the application area. 2. Select the check box for each alert that you want to delete. To select all check boxes, click the Select All button. 3. Click the Delete button. A window appears asking you to confirm that you want to delete the selected alert(s). 4. Click the OK button to delete the selected alert(s), or the Cancel button to cancel the deletion. The selected alert(s) are deleted from the Device Manager server.
5-5 Viewing the task list

The Device Manager enables the user to view task information within the limits of the user's permissions. To view the Device Manager Task List, select Tasks from the Explorer menu to open the Tasks subwindow in the application area. The Tasks subwindow displays the following information for each item listed:
Operation: Name of the operation performed by the user Subsystem: Name of the storage subsystem involved in the operation Logical Group: Name of the logical group(s) involved in the operation Start Time: Date and time that the operation was started
NOTE: When operations are performed on a storage subsystem from Physical View, no task information is displayed in the Tasks subwindow. If a task is being executed from Physical View, Busy is displayed in Physical View. You can perform the next operation when the Busy indication disappears.
82
5-6 Launching other applications from the Device Manager

The Device Manager provides link-and-launch functionality for the following applications:
HDLM (see section 5-6-1 ) XP Provisioning Manager software (see section 5-6-2 ) XP Tiered Storage Manager software (see section 5-6-3 ) Launching XP Replication Monitor software (see section 5-6-4 ) XP Remote Web Console (see section 5-6-5 ) HP Storage Essentials (see section 5-6-6 ) NAS Manager (see section 5-6-7 ) Third-party application (see section 5-6-8 )
CAUTION: If you launch more than one instance of XP Command View AE Suite software, make sure that no operations are in progress before logging out. If you log out on the global tasks bar area of another XP Command View AE Suite software that you launched using the link-andlaunch feature, you will also be logged out from Device Manager and will not be able to operate Device Manager.
5-6-1 Launching HDLM

HDLM manages access paths to storage for the StorageWorks XP Disk Array subsystems. HDLM provides functions for distributing workload across paths and switching to an alternate path if a failure occurs on the path in use. Networks dedicated to data transfer, such as storage area networks (SANs), can use HDLM to provide enhanced access to storage. When a Device Manager agent and Dynamic Link Manager are installed on Device Manager's management-target host, a Dynamic Link Manager button appears in the host-name subwindow that displays host properties. For instructions for displaying the host-name subwindow for a host, see section 9-5 . To launch the HDLM GUI, click the Dynamic Link Manager button. To launch HDLM so that it opens displaying a specific volume path, select the desired volume path in the host-name subwindow and then click the Dynamic Link Manager button. You can select only one volume path. For details about the selectable volume types, see the descriptions of the devices that HDLM can manage in the respective user documentation.
5-6-2 Launching XP Provisioning Manager software

XP Provisioning Manager software allows you to manage a group of disks in a storage subsystem as a single large data storage pool. XP Provisioning Manager software can be launched from the dashboard menu.
5-6-3 Launching XP Tiered Storage Manager software

XP Tiered Storage Manager software allocates data to the best-suited storage based on the data characteristics (value of data and access frequency) in a hierarchical storage environment with XP24000/XP20000 or XP12000/XP10000/SVS200 as the core. XP Tiered Storage Manager software can be launched from the dashboard menu.
83
5-6-4 Launching XP Replication Monitor software

XP Replication Monitor software provides the functionality for monitoring the configuration and operating status of complex copy pairs in an easy-to-understand manner and automatically notifies users if an error occurs. XP Replication Monitor software can be launched from the dashboard menu.
5-6-5 Launching XP Remote Web Console (XP1024/XP128)

When XP Remote Web Console is installed on an XP1024/XP128 that is registered in Device Manager, it can be started from the web client by a user assigned to the All Resources resource group. IMPORTANT: When using Mozilla in a Solaris or HP-UX environment, you must configure the browsers and Java plug-ins you use to start XP Remote Web Console. For details on how to configure browsers and Java plug-ins, see section 4-2-2 . IMPORTANT: To start XP Remote Web Console, the Java heap size must be set to 256 MB. For details on how to set the Java heap size for XP Remote Web Console, see the XP Remote Web Console manual.
You can start XP Remote Web Console from the following places:
From the Physical View. For XP1024/XP128, the XP Remote Web Console drop-down list appears in the Physical View dialog box. For details on the Physical View dialog box, see section 10-2-3 . If you have Modify permission, you can select the function from the list of licensed functions in the XP Remote Web Console. If you have been granted only the View permission, only Login appears in the drop-down list. When you select Login, the login window for XP Remote Web Console appears.
From the subsystem-name subwindow. For XP1024/XP128, the XP Remote Web Console button appears in the subsystem-name subwindow. For details on the subsystem-name subwindow, see section 10-1-3 . If you have Modify permission, the main window of XP Remote Web Console appears, allowing you to use the licensed features. If you have only View permission, the login window for XP Remote Web Console appears.
5-6-6 Launching HP Storage Essentials

HP Storage Essentials acts as the main console for heterogeneous storage infrastructure management software, providing SAN visualization and reporting, asset management, performance and capacity monitoring and planning, and policy-driven event management. HP Storage Essentials can be launched from the dashboard menu.
5-6-7 Launching NAS Manager (XP12000/XP10000/SVS200 and XP1024/XP128)

When a NAS-CHA running NAS Manager resides on an XP12000/XP10000/SVS200 or XP1024/XP128 subsystem managed by Device Manager, you can launch NAS Manager from web client if you have been assigned to the All Resources resource group and have the Modify permission. You can start NAS Manager from either of the two windows, depending on the storage subsystem:
From the Physical View for XP1024/XP128
84
Performing Device Manager system operations In the Physical View for XP1024/XP128, select NAS-CHA from the NAS/Management dropdown list. For details on how to open the Physical View, see section 10-2-3 .
subsystem-name subwindow for XP12000/XP10000/SVS200 or XP1024/XP128 In the subsystem-name subwindow for XP12000/XP10000/SVS200 or XP1024/XP128, click the NAS/Management button. The Select Nas/Management Port Controller dialog box appears. The list of selectable NAS-CHAs is sorted and then displayed. Select NAS-CHA and then click the OK button to launch NAS Manager. For details on how to open the subsystemname subwindow, see section 10-1-3 .
5-6-8 Launching a third-party application

When third-party software applies to a specific array, the Device Manager provides a URLLink that allows you to link-and-launch from the Physical View or subsystem-name subwindow to a URL specific to the storage subsystem. Only a user who is assigned to the All Resources resource group and has Modify permission can use URLLink. For details, see the AddURLLink, GetURLLink, and DeleteURLLink API commands in HP StorageWorks XP Command View Advanced Edition software Device Manager CLI user guide NOTE: URLs that you set using URLLink are displayed in the HTML source code.
5-7 Downloading Device Manager software

The web client enables you to download Device Manager software from the Device Manager server to the local environment. You can download the following software:
Device Manager agent Device Manager Command Line Interface (CLI) The JRE required for the execution environment of the selected software
Software is provided in a compressed file for each type of platform. For Windows, software is in the exe format (self-extracting). For UNIX, software is in the tar format. Expand the desired software from a file that is suited to your platform and then install it. Download the software suited to your platform, extract the downloaded software to the machine where you want to install the software and then install it. To download and install software: 1. In the global tasks bar area, select Go and then Download. The Device Manager Software Deployment dialog box appears, displaying the Download, ReadMe and JRE links for each platform of the provided software. 2. Click the ReadMe link for the appropriate platform to review how to install the software. 3. A JRE is required to execute the software. If you do not have a JRE, download one from the website of a vendor suited to your platform. 4. Click the Download link suited to your platform for the software you want to download. A dialog box for downloading the file appears. 5. Check the message in the download dialog box and click the Save button. The Save As dialog box appears. 6. In the Save As dialog box, specify the desired storage destination and then save the file. 7. Install the software. For the installation procedure, see the following manuals:
For the Device Manager agent

HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide 85
For the Device Manager Command Line Interface (CLI)

HP StorageWorks XP Command View Advanced Edition software Device Manager CLI user guide
86

This chapter describes Device Manager user management operations.
Overview of user management operations (see section 6-1 ) User management operations (see section 6-2 ) Resource group operations (see section 6-3 ) Setting security options for login (see section 6-4 ) Migration from an earlier version (see section 6-5 )
6-1 Overview of user management operations

In the Device Manager, you can set user permissions to restrict the operations that can be performed by individual users. You can also restrict the resources accessed by users by assigning resource groups to each user. For details about permissions, see section 2-1-1 . For details about resource groups, see section 2-1-2 . The Device Manager supports functions that enhance the security when a user logs in. For details on the security enhancing functions available, see section 6-4 . The Administration menu is available when you log in with User Management permission or Admin permission. To manage users and operate resource groups, in the Explorer menu select Administration. To create a new user: 1. Create a new user (see section 6-2-1 ). 2. Set permissions for the new user (see section 6-2-2 ). 3. Create a resource group (see section 6-3-1 ). You can also create a resource group before creating a new user in step 1. 4. Assign the resource group to the new user (see section 6-3-2 ).
6-2 User management operations

With User Management permission, you can perform operations on any user account. Without User Management permission, you can modify only your own profile (full name, e-mail address, and description) and your password. The Device Manager user account operations include:
Creating a user (see section 6-2-1 ) Viewing and changing user permissions (see section 6-2-2 ) Viewing and editing user profiles (see section 6-2-3 ) Changing your password (see section 6-2-4 ) Changing the lock status of a user account (see section 6-2-5 ) Deleting a user (see section 6-2-6 )
87
6-2-1 Creating a user

With User Management permission, you can create a user account common to the XP Command View AE Suite as required. To create a new user account: 1. In the Explorer menu, select Administration and then Users and Permissions. 2. In the navigation area, select Users. The Users subwindow appears, displaying the current list of users. 3. Click the Add User button in the Users subwindow. The Add User dialog box is displayed. 4. Enter the following information for the new user:
User ID. The user ID (login name) may be 1 to 256 characters in length and is not casesensitive (thus, for example, if "USER1" already exists, you cannot create "user1"). You can use the following characters: A-Z a-z 0-9 # + - _ . @ NOTE: On XP Command View AE Suite earlier than version 5.5, the number of characters that can be set for a user ID is between 4 bytes and 25 bytes. For environments that contain XP Command View AE Suite of version 5.5 or later, together with products earlier than version 5.5, set a user ID using between 4 bytes and 25 bytes.
Password and Verify Password. The password may be a maximum of 256 characters in
length and is case-sensitive. You can use the following characters: A-Z a-z 0-9 ! # $ % & ' ( ) * + - . = @ \ ^ _ | If conditions have been set in your system establishing the minimum number of characters or combination of characters that are allowed for a password, you can only set passwords that meet these conditions. For information on any such conditions, contact your system administrator. NOTE: On XP Command View AE Suite earlier than version 5.5, the number of characters that can be set for a password is between 4 bytes and 25 bytes. For environments that contain XP Command View AE Suite of version 5.5 or later, together with products earlier than version 5.5, set a password using between 4 bytes and 25 bytes.
Full Name (optional)

The full name can contain up to 80 characters. The following characters may be used (Unicode 0020 to 007E): A-Z a-z 0-9 ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~ (space) Do not use two or more dollar signs ($) consecutively (for example, $$ or $$$). NOTE: The full name is displayed in the global tasks bar area after a user logs in. If the full name is omitted during the set up, the user ID will be displayed in the global tasks bar area instead.
E-mail (optional)
Enter up to 255 alphanumeric characters.
Description (for example, job title) (optional)

Enter up to 80 characters, using the character set allowed for the full name. 5. Click the OK button to save the settings. The user account is created and you are returned to the Users subwindow. The new user account appears in the User List. 88
NOTE: The new user cannot access Device Manager yet because he or she does not have any permissions or resource group. To enable the new user to access Device Manager, you must set permissions and assign a resource group to the user. For details about setting permissions, see section 6-2-2 . For details about assigning resource groups, see section 6-3-2 .
6-2-2 Setting permissions for a user

With User Management permission, you can set permissions for users other than yourself to access Device Manager and other XP Command View AE Suite. Observe the following rules when setting user permissions:
You cannot change the permissions associated with the System account. Do not change the permissions for the HaUser account. This account is the default user for the Device Manager agent. The User Management permission does not allow you to change your own permissions. To change your own permissions, you must log in to Device Manager using the System account or the user ID of another user who has the User Management permission.
To set permissions for a user: 1. In the Explorer menu, select Administration and then Users and Permissions. 2. In the navigation area, expand the Users object tree and select the user ID for which you want to set permissions. The user-ID subwindow appears in the application area, displaying any permissions already set for the user (see Figure 6-1).
Figure 6-1 User-ID subwindow 3. To change permissions, click the Change Permission button. The Change Permissionuser-ID dialog box appears (see Figure 6-2).
89
Figure 6-2 Change Permissionuser-ID dialog box 4. For each application, select the permissions you want to set for the user and then click the OK button to save the settings. For the combinations of permissions you can set, see section 2-1-1 . IMPORTANT: Resource groups assigned to users remain in effect until the assignment is cleared. If you clear a user's permission to access the Device Manager and then reinstate permission for the same user again, the resource groups originally assigned to the user will still be in effect.
6-2-3 Viewing or editing a user profile

With User Management permission, you can view and edit the profile of any user. Without User Management permission, you can view and edit only your own profile. The procedures for viewing or editing a profile are described below.
6-2-3-1 Viewing or editing another user's profile

To view or edit another user's profile: 1. Log in to Device Manager using an account that has User Management permission. 2. In the Explorer menu, select Administration and then Users and Permissions. 3. In the navigation area, expand the Users object tree and select the user ID of the user whose profile you want to view or edit. The user-ID subwindow appears in the application area, displaying the user's profile and permissions (see Figure 6-1). 4. To edit the profile, click the Edit Profile User button. The Edit Profile Useruser-ID dialog box appears. In this dialog box, you can edit the Full Name, E-mail, and Description settings. 5. Make sure changes are correct,, then click the OK button to save the new settings and update the user's profile information in the user-ID subwindow.
90
6-2-3-2 Viewing or editing your own profile

To view or edit your own profile: 1. Log in to Device Manager with any user ID. 2. In the Explorer menu, select Settings and then User Profile. The User Profile subwindow appears in the application area displaying the profile and permissions of the user account you logged in with. 3. To edit the profile, click the Edit Profile button. The Edit Profileuser-ID dialog box appears. To change your profile, edit the Full Name, E-mail, and Description settings. 4. Click the OK button to save the edited settings. The edited information is reflected in the User Profile subwindow.
6-2-4 Changing passwords

With User Management permission, you can change the password of any user. Without User Management permission, you can change only your own password. CAUTION: When the Device Manager server is running in a cluster environment, if you change the password for the System account, specify the same settings on all nodes that make up the cluster. For details about cluster environments, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide.
The procedures for changing a password are described below.
6-2-4-1 Changing another user's password

To change another user's password: 1. Log in to Device Manager with a user account that has User Management permission. 2. In the Explorer menu, select Administration and then Users and Permissions. 3. In the navigation area, expand the Users object tree and select the user ID whose password you want to change. The user-ID subwindow appears in the application area. 4. Click the Change Password button. The Change Passworduser-ID dialog box appears. 5. Type the new password in the New Password and Verify Password text boxes and then click the OK button. The password may be a maximum of 256 characters in length and is case-sensitive. You can use the following characters: A-Z a-z 0-9 ! # $ % & ' ( ) * + - . = @ \ ^ _ | If conditions have been set in your system establishing the minimum number of characters or combination of characters that are allowed for a password, you can only set passwords that meet these conditions. For information on any such conditions, contact your system administrator. NOTE: On XP Command View AE Suite earlier than version 5.5, the number of characters that can be set for a password is between 4 bytes and 25 bytes. For environments that contain XP Command View AE Suite of version 5.5 or later, together with products earlier than version 5.5, set a password using between 4 bytes and 25 bytes.
91
6-2-4-2 Changing your own password

To change your own password: 1. Log in to Device Manager using any user account. 2. In the Explorer menu, select Settings and then User Profile. The User Profile subwindow appears in the application area. 3. Click the Change Password button. The Change Passworduser-ID dialog box appears. 4. Type your current password in the Old Password text box. Type your new password in the New Password and Verify Password text boxes and then click the OK button. The password may be a maximum of 256 characters in length and is case-sensitive. You can use the following characters: A-Z a-z 0-9 ! # $ % & ' ( ) * + - . = @ \ ^ _ | Set conditions might apply to the minimum number of characters or combination of characters that can be set as a password. Passwords that do not meet these conditions cannot be set. For information on the set conditions, contact your system administrator. NOTE: On XP Command View AE Suite earlier than version 5.5, the number of characters that can be set for a password is between 4 bytes and 25 bytes. For environments that contain XP Command View AE Suite of version 5.5 or later, together with products earlier than version 5.5, set a password using between 4 bytes and 25 bytes.
6-2-5 Changing the lock status of a user account

When a user account is locked, the user cannot log in to any products in the XP Command View AE Suite. Users with User Management permission can lock and unlock user accounts manually. However, users with User Management permission cannot lock their own user account. Users who have User Management permission can also unlock user accounts that were locked automatically because of repeated login failures. For details on how to lock a user account automatically, see section 6-4-2 . The System account cannot be locked. CAUTION: Before locking a user account, make sure the user is not logged in to Device Manager. If you lock the account of a user who is currently logged in, the user will not be able to perform any operations.
To change the lock status of a user account: 1. In the Explorer menu, select Administration and then Users and Permissions. 2. Select a user in the navigation area. The Users subwindow appears, and shows the User List. 3. To change the lock status of a selected user, in the User List, select the check box of the user whose account lock status you want to change, and then click the Lock Users or Unlock Users button. To change the lock status of all user accounts, click the check box in the title bar. A message asks you to confirm that you want to change the lock status for the user account. 4. Click the OK button to change the account status, or the Cancel button to cancel the change. You are returned to the Users subwindow. If you changed the lock status, the Status field is updated in the User List.
92
6-2-6 Deleting users

With User Management permission, you can delete a user account common to the XP Command View AE Suite as required. Observe the following rules when deleting a user account:
Do not delete the HaUser account. This account is the default user for logging in to the Device Manager agent. If you delete this account, the Device Manager agent cannot transmit information to the Device Manager server. You cannot delete the System account. Before deleting any account, make sure the user is not logged in to Device Manager. If you delete a user who is currently logged in, that user will be unable to continue operations.
To delete a user from the Device Manager server: 1. In the Explorer menu, select Administration and then Users and Permissions. 2. In the navigation area, select Users. The Users subwindow appears displaying the User List. 3. In User List, select the check box of the user that you want to delete and then click the Delete Users button. To delete all listed user accounts, click the check box in the title bar. A confirmation window displays the confirmation message. IMPORTANT: To delete a user after viewing the user's profile, select the required user ID in User List and open the user-ID subwindow. In the user-ID subwindow, you can click the Delete User button to delete that account. 4. Click the OK button to delete the account, or the Cancel button to cancel deletion.
6-3 Resource group operations

With Admin permission, you can manage resource groups. By creating resource groups and assigning them to users, you can control the Device Manager resources that users are allowed to access. The Device Manager resource group operations include:
Creating a resource group (see section 6-3-1 ) Assigning a resource group to a user (see section 6-3-2 ) Viewing and changing resource group properties (see section 6-3-3 ) Deleting a resource group (see section 6-3-4 )
6-3-1 Creating a resource group

With Admin permission, you can create resource groups as required. If you are assigned to the All Resources resource group, you can create a resource group allowing access to all Device Manager resources. If you are assigned a user-defined resource group, you can create a new resource group under your assigned resource group. When you create a resource group, you allocate the logical group, hosts, and LDEVs that the user can access to the group. Note that the following logical groups cannot be associated with a resource group:
A logical group allocated to another resource group A logical group that has a lower-level logical group allocated to another resource group A storage group
93
CAUTION: Before you create a new resource group, make sure that the logical group to be associated with the resource group has been created in Device Manager (see section 7-3 ). You cannot change the associated logical group after creating a resource group.
To create a Device Manager resource group: 1. In the Explorer menu, select Administration and then Resource Groups. 2. In the application area, select Resource Group Administration. The Resource Group Administration dialog box appears (see Figure 6-3).
Figure 6-3 Resource Group Administration dialog box 3. Click the CREATE button to open the Resource Group Properties dialog box (see Figure 6-4).
Figure 6-4 Creating a resource group
94
Performing user management operations 4. Complete the Group Name and Description text boxes for the new resource group you are creating.
Group Name (mandatory)

The resource group name can be up to 25 bytes in length and cannot contain any spaces. You can use the following characters: A-Z a-z 0-9 , - . = \ _ `
Description (optional)
The description can be up to 255 bytes in length and can contain the following characters and spaces (Unicode 0020 to 007E): A-Z a-z 0-9 ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~ (space) 5. Click the Logical Group tab and select a logical group to be allocated to the new resource group. Users assigned to this resource group will be able to access all LUNs in the group and any logical groups below this group. 6. Click the Host tab and select the hosts to be allocated to the new resource group. The hosts allocated to the LUNs in the logical group selected in step 5 are automatically displayed in the list of Accessible hosts on the Host tab. You cannot delete these hosts from Accessible hosts. To add another host, select the host you want to add from Inaccessible hosts and then click the Add button. To allow copy pair operations to be performed by the users to whom this user-defined resource group is assigned, make sure that you allocate to the resource group a host that meets the requirements for such operations and a command device recognized by that host. CAUTION: If you are using XP External Storage Software from a storage subsystem, and the storage subsystem has been incorrectly added to Device Manager, the external port might appear as a host under Inaccessible hosts or Accessible hosts. You must not allocate an external port to a resource group. If you refresh a storage subsystem that uses XP External Storage Software when an external port is allocated to a resource group, the external port disappears from the Inaccessible hosts or Accessible hosts list and is unallocated from the resource group. To find whether a host listed under Inaccessible hosts or Accessible hosts is an external port, from the Explorer menu, select Resources and then Hosts to display the Host Management window. If the host you are interested in is displayed under the External Array Nodes object, it is an external port. 7. Click the LDEV tab and select the LDEVs to be allocated to the resource group. The LDEVs corresponding to the path in the logical group selected in step 5 are automatically displayed in Accessible LDEVs list on the LDEV tab. You cannot delete these LDEVs from Accessible LDEVs. To add another LDEV, select a storage subsystem from Select subsystem, select the LDEV you want to add from the LDEVs displayed in Inaccessible LDEVs and then click the Add button. 8. Make sure that the logical group, host, and LDEV information is correct, and then click the SAVE button to save your changes. The Device Manager creates the new resource group and returns you to the Resource Group Administration dialog box where the new resource group is now listed.
6-3-2 Assigning a resource group to a user

With Admin permission, you can assign All Resources or a user-defined resource group to a user. To assign a user-defined resource group to a user, you must create a resource group in advance. For details about creating resource groups, see section 6-3-1 . Observe the following rules when assigning a resource group to a user: 95
You cannot change the resource group associated with the System account. You cannot assign a resource group to a user who the has Peer permission.
To assign a resource group to a user: 1. In the Explorer menu, select Administration and then Resource Groups. 2. In the application area, select Resource Group Allocation. The Resource Group Allocation dialog box appears, displaying the resource group allocated to each user (see Figure 6-5).
Figure 6-5 Resource Group Allocation dialog box 3. Select the user account to which you want to assign a resource group or whose assigned resource group you want to change. Then click the CHANGE button. The Change Resource Group dialog box appears (see Figure 6-6).
96
Figure 6-6 Change Resource Group dialog box 4. From the Resource Group drop-down list, select a resource group to assign to the user.
User-defined resource groups

If you are logged in with an account to which All Resources is assigned, all resource groups are listed. If you are logged in with an account to which a user-defined resource group is assigned, only the resource groups that you can access are shown.
All Resources
Select All Resources to allow the user to access all Device Manager resources.
No Group
Select <No Group> to clear a resource group allocated to the user. The user will be unable to log in to Device Manager without User Management permission. 5. Click the OK button to allocate the resource group. The information in the Resource Group Allocation dialog box is updated.
6-3-3 Viewing or editing resource group properties

With Admin permission, you can edit the properties of user-defined resource groups, but cannot change the properties of All Resources. The following describes the resource groups whose properties can be edited.
If you are assigned to the All Resources resource group, you can edit the properties of any user-defined resource group. If you have been assigned to a user-defined resource group, you can edit the properties of your assigned resource group and of any lower-level resource groups.
To view and edit the properties of a Device Manager resource group: 1. In the Explorer menu, select Administration and then Resource Groups. 2. In the application area, select Resource Group Administration to open the Resource Group Administration dialog box (see Figure 6-3). 3. Select a resource group and then click the EDIT button to open the Resource Group Properties dialog box. In this dialog box, you can view the resource group properties and the resources allocated to the resource group (see Figure 6-7).
97
Figure 6-7 Changing resource group properties 4. Change the settings in the Resource Group Properties dialog box as required. You can edit the information on the Description, Host, and LDEV tabs. You cannot change the resource group name or the logical group allocated to the resource group. NOTE: If you are using XP External Storage Software from a storage subsystem, take care when performing host allocation. 5. Click the SAVE button to save your changes and update the resource group properties.
6-3-4 Deleting a resource group

With Admin permission, you can take the following delete actions:
You can delete a user-defined resource group as required. You cannot however, delete All Resources. If All Resources has been assigned as your resource group, you can delete any user-defined resource group. If you are assigned a user-defined resource group, you can delete only the resource groups under your assigned resource group. If you delete a resource group assigned to a user who does not have User Management permission, that user will be unable to log in to Device Manager. If you delete a resource group assigned to a user who has logged in to Device Manager, an error occurs the next time that user performs an operation. Before deleting a resource group, make sure that the user to whom the resource group is assigned has not logged in to Device Manager. If the resource group you are deleting has any lower-level resource groups, they will also be deleted.
Consequences of deleting certain types of resource group assignments:
To delete a resource group from the Device Manager server: 1. In the Explorer menu, select Administration and then Resource Groups.
98
Performing user management operations 2. In the application area, select Resource Group Administration to open the Resource Group Administration dialog box (see Figure 6-3). 3. Select the resource group you want to delete and then click the DELETE button. A confirmation message appears. 4. Click the YES button to delete the selected resource group, or the NO button to cancel.
6-4 Setting security options for login

To enhance security when a user logs in, users who have the User Management permission can set the following security options for login:
Password conditions (see section 6-4-1 ) Automatic locking of user accounts (see section 6-4-2 ) A warning banner message (see section 6-4-3 )
NOTE: If you run the Device Manager server in a cluster environment, set the security options on the server. For details on how to set the security options, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide. CAUTION: Whenever you use web client to change the password condition settings or the setting for automatically locking user accounts, the security options settings file is overwritten. If you intend to manually edit the settings file, we recommend that you back up the file beforehand. For details on how to edit the settings file manually, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
6-4-1 Setting password conditions

Users who have the User Management permission can set password conditions. To prevent users' passwords from being guessed by a third party, Device Manager enables password conditions (the minimum number of characters and the combination of characters that can be used) to be specified. The password conditions apply when a user account is added or a password is changed, and are not applied to passwords of existing user accounts. To set password conditions: 1. In the Explorer menu, select Administration and then Security. In the navigation area, select Password. The Password subwindow appears in the application area. The Password subwindow displays the set password conditions. 2. To change the password conditions, click the Edit Settings button. The Password dialog box appears (see Figure 6-8).
99
Figure 6-8 Setting password conditions 3. Enter the following information to set the password conditions.
Minimum length
Specify the minimum number of characters that can be set as a password. The available range is 1 to 256 characters. The default is 4 (characters).
Minimum number of characters

Specify the minimum number of characters for uppercase, lowercase, numeric, and symbolic characters that must be included in a password. You must specify the values so that the total number of uppercase, lowercase, numeric, and symbolic characters does not exceed the minimum length that can be specified for a password. You can specify from 0 to 256 characters. The default is 0 (characters).
Allow password to be the same as the User ID

The default is Yes. If you select No, a user cannot use his or her user ID as a password 4. To change the password conditions, click the OK button. To cancel modification of the password conditions, click the Cancel button. You are returned to the Password subwindow. The password conditions are updated to reflect the new settings.
6-4-2 Setting automatic locking for user accounts

Users who have the User Management permission can set automatic locking of user accounts. When automatic locking has been set for a user account, operations by a user can be automatically locked if an invalid password is entered repeatedly for that user account. When enabling automatic locking of a user account, you can specify the number of login failures allowed before the user account is automatically locked. Unsuccessful attempts to log in to other products in the XP Command View AE Suite that use the Single Sign-On feature count towards the number of unsuccessful login attempts. For example, if the number of unsuccessful attempts is set to 2, and a user fails to log in to Device Manager once and then fails to log in to XP Provisioning Manager software once, the user account will be automatically locked. Changing the number of unsuccessful login attempts does not affect current users who have already registered a number of unsuccessful attempts or whose user account is locked. For example, if you change the number of unsuccessful login attempts from 5 to 2, the user account of a 100
Performing user management operations current user who has already made three unsuccessful login attempts will remain active. If that user fails the next login attempt, the user account for that user will be locked. When a user account is locked, the user cannot log in to any products in the XP Command View AE Suite until the user account is unlocked. For details on how to unlock a user account, see section 62-5 . NOTE: Even when automatic locking has been set, the System account is not locked.
To set automatic locking of a user account: 1. In the Explorer menu, select Administration and then Security. In the navigation area, select Account Lock. The Account Lock subwindow appears in the application area. When automatic locking of a user account has been set in the Account Lock subwindow, the number of allowable consecutive login failures is displayed. If automatic locking has not been set, the Account Lock subwindow indicates unlimited. 2. To change the automatic lock setting, click the Edit Settings button. The Account Lock dialog box appears (see Figure 6-9).
Figure 6-9 Setting automatic account locking 3. In the Account Lock dialog box, change the automatic lock setting for the user account. To enable automatic locking of the user account, select Lockout a user account after number of failed attempts and then enter a value between 1 and 100 in Maximum number of login attempts. 4. Click the OK button to enable the change to the automatic lock setting for the user account. To cancel the change to the automatic lock setting, click the Cancel button. You are returned to the Account Lock subwindow. The automatic lock setting for the user account is updated.
6-4-3 Setting a warning banner message

Users who have the User Management permission can set a warning banner message. As a security measure at login, Device Manager enables you to set any message in the Login window. NOTE: You can also use the hcmdsbanner command to set a warning banner message. When you set a message using the hcmdsbanner command, there are no restrictions on the HTML tags that you can use. You can even set different messages for different locales. For details on how to set a warning banner message using the hcmdsbanner command, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide. 101
NOTE: In the web client, you can only edit the warning banner message that is displayed as the default. You cannot edit a message that was set using the hcmdsbanner command if the message contains HTML tags that are not allowed in the web client.
To edit the warning banner message: 1. In the Explorer menu, select Administration and then Security. 2. In the navigation area, select Warning Banner. The Warning Message subwindow is displayed in the application area. The current message appears in the Warning Banner subwindow. If no message has been set, the Warning Banner subwindow indicates No Message. 3. To edit the message, click the Edit Message button. The Edit Message dialog box appears. 4. In the Message text box, set the desired warning banner message (To delete the set message, click the Delete button). The message must be edited in HTML format. The maximum number of characters that you can use, including the HTML tags, is 1,000. When editing the message in the web client, you can use only the following HTML tags: <b> </b> <i> </i> <center> </center> <br> <div dir="ltr"> <div dir="rtl"> <div style="direction:rtl"> <div style="direction:ltr"> </div> HTML tags are not case sensitive. To insert a line feed into the message to be displayed, use the HTML tag <br> at the desired position. Line feed characters that you enter when editing the message are ignored at registration. To display characters used as HTML tags in the message, use the HTML escape sequence. 5. To check the edited message, click the Preview button. If the message has been edited correctly, the HTML image of the message appears in the Preview box (see Figure 6-10). If you have used tags that cannot be used or if there is a problem in the HTML syntax, an error message appears and Preview is blank.
102
Figure 6-10 Warning banner message edited correctly 6. Once you have confirmed that the message is displayed correctly, click the OK button to save the editing changes. To cancel editing of the message, click the Cancel button.
6-5 Migration from an earlier version

When you upgrade to Device Manager version 5.0 or later from version 4.3 or earlier, the user roles, user groups, and properties set for users in the earlier version are migrated to the version 5.0 or later format. IMPORTANT: For details about migrating the user ID and password associated with the upgrade, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide.
6-5-1 Migrating user roles

The user roles in the earlier version are migrated to the permissions for version 5.0 or later. A combination of 5.0 permissions corresponding to the particular user role are set for each user. Table 6-1 describes the migration of user roles.
103
Performing user management operations Table 6-1 Migration of user roles User role in earlier version User Device Manager permissions Management Admin
System Administrator Local System Administrator* Storage Administrator Local Storage Administrator Guest Local Guest Peer Yes No No No Yes No No No
Modify
Yes Yes No No
View
Yes Yes Yes No
Peer
No No No Yes
Legend: Yes = The user has the permission. No = The user does not have the permission. * When the Local System Administrator account is migrated to version 5.0 or later from an earlier version, users who have the Local Systems Administrator role can exercise the User Management permission on all users (not just on users who belong to the same resource group as the Local Systems Administrator or its subordinate resource groups). As with earlier versions, however, you can only manage resource groups that belong to your resource group.
6-5-2 Migrating user groups

When the Local System Administrator, Local Storage Administrator, and Local Guest accounts are migrated to version 5.0 or later from an earlier version, the user groups previously assigned to the users become user-defined resource groups. When the System Administrator, Storage Administrator, and Guest accounts are migrated to the 5.0 environment, All Resources is assigned as their resource group.
6-5-3 Migrating user properties

Table 6-2 describes the migration of properties set in an earlier version. Table 6-2 Migration of user properties Version 4.3 or earlier
First name and last name Description
Version 5.0 or later

Full name Description
Migration
Converted to a full name in the format <firstname> <last-name> Unchanged
NOTE: After the migration, if the number of the characters in Full Name or Description exceeds the maximum allowed, you must edit the user profile so that the number of specified characters does not exceed the maximum.
104
Performing logical group operations

This chapter describes logical group operations:
Overview of logical groups (see section 7-1 ) Viewing the list of logical groups (see section 7-2 ) Creating a logical group (see section 7-3 ) Viewing and editing logical group properties (see section 7-4 ) Deleting a logical group (see section 7-5 ) Storage group operations (see section 7-6 )
7-1 Overview of logical groups

In the Explorer menu, select My Groups and then Logical Groups to display the Logical Groups object tree in the navigation area. The Logical Groups object in the navigation area allows you to access logical group operations. Logical groups can be classified as follows:
Parent or child group: When logical groups are arranged in a hierarchical structure, a higherlevel logical group in the hierarchy can be called a parent group, and a lower-level logical group in the hierarchy can be called a child group. A parent group is always a logical group, whereas a child group can be either a logical group (such as mid-level) or a storage group. Storage group: A logical group for which paths to storage have been set is called a storage group. A storage group is a collection of any user-specified LUNs (access paths). Storage groups are placed under logical groups. However, logical groups cannot be placed under storage groups. Empty group: A logical group that has no contents is called an empty group. An empty group can be converted to a storage group by assigning storage to it or to a parent group by assigning a logical group to it.
Device Manager enables you to create a hierarchy of logical groups and assign storage to empty groups or storage groups. One or more logical groups and/or one or more storage groups can be placed in a logical group. The All Storage or My Storage object contains all LDEVs that can be accessed by the logged-in user. The All Storage object appears when a user assigned the All Resources resource group has logged in. The My Storage object appears when a user assigned to a user-defined resource group has logged in. The All Storage or My Storage object has a group for each storage subsystem, and each storage subsystem group contains an Open-Allocated group, an Open-Unallocated group, an Open-Reserved group and a Mainframe-Unspecified group. For XP24000/XP20000, each storage subsystem group contains a Pools group.
Open-Allocated group: Displays the LUs or LDEVs that are available to the logged-in user, and that have one or more paths assigned, on open volumes in the specified storage subsystem. When you add a new storage subsystem or perform a Refresh on an existing storage subsystem (see section 10-1-4 , the LUs or LDEVs that have paths assigned to open volumes are placed in the Open-Allocated group. Open-Unallocated group: Displays the LUs/LDEVs that are available to the logged-in user, and that do not have any paths assigned, on open volumes in the specified storage subsystem. When you add a new storage subsystem or perform a Refresh on an existing storage subsystem (see section 10-1-4 ), the LUs or LDEVs that do not have any paths assigned to open volumes are placed by Device Manager into the Open-Unallocated group.
105
Open-Reserved group: Displays the LUs/LDEVs that are available to the logged-in user, and that cannot be assigned any paths on open volumes in the specified storage subsystem. When you add a new storage subsystem or perform a Refresh on an existing storage subsystem (see section 10-1-4 ), the LUs or LDEVs that cannot be assigned any paths to open volumes are placed by Device Manager into the Open- Reserved group. Mainframe-Unspecified group: Displays the mainframe volumes that are available to the logged-in user in the specified storage subsystem. When you add a new storage subsystem or perform a Refresh on an existing storage subsystem (see section 10-1-4 ), mainframe volumes are placed in the Mainframe-Unspecified group. Pools group: Displays the pools that can be managed by Device Manager in the specified storage subsystem. When you add a new storage subsystem or perform a Refresh on an existing storage subsystem (see section 10-1-4 ), pools are placed in the Pools group. The Pools group is displayed for XP24000/XP20000 storage subsystems.
7-2 Viewing the list of logical groups

All Device Manager users can view the list of logical groups for which they have access permission. To view the list of logical groups, in the Explorer menu select My Groups and then Logical Groups and then select the Logical Groups object in the navigation area. You can expand the tree hierarchy as necessary to display the child group(s) and/or storage group(s) contained within the parent group(s). When the Logical Groups object is selected in the navigation area, the application area displays the list of objects (logical groups and/or storage groups) at the top level of the logical group hierarchy. When a logical group is selected in the navigation area, the application bar area displays the Delete Group and Modify Properties buttons, and the application area displays the following subwindows:
Logical Group: Displays the properties of the selected logical group:
Name: Name of the logical group Parent group: Name of the parent group with nested child groups. Groups are separated
by a slash (/); for example, /Enterprise/MIS Dept/E-Mail.
Number of LUNs: Total number of LUNs in the logical group, including the LUNs in all
child groups
Configured Capacity: Total capacity of the storage in the logical group, including the
storage in all child groups
Subsystem: Subsystem name for storage that is allocated to a storage group. This item is
displayed only for storage groups.
A list of child groups or storage: Displays the list of objects contained in the selected logical group. If a parent group is selected in the navigation area, Object List is displayed in the item name, and this subwindow displays the child groups (logical groups and/or storage groups) contained within the selected logical group. If a storage group is selected in the navigation area, this subwindow displays a list of LUNs contained in the storage group.
7-3 Creating a logical group

Logical groups can contain one or more logical groups and/or storage groups. Users with Modify permission can create logical groups. NOTE: Logical groups created on the 32nd level or higher are not displayed in the navigation area. We recommend that you create no more than 31 levels for a logical group hierarchy. To create a logical group to Device Manager: 1. In the Explorer menu, select My Groups and then Logical Groups.
106
Performing logical group operations 2. Expand the tree in the navigation area as necessary and then in the navigation area, select the parent group for the logical group that you want to create. To create a logical group at the top level, select the Logical Groups object. 3. In the application area, click the Create Group button. The Create Group window appears as shown in Figure 7-1. The parent group selected in the navigation area is displayed in Parent Group. If you select the Logical Groups object in the navigation area, None is displayed.
Figure 7-1 Creating a logical group 4. In the Create Group window, enter a new group name in the Group Name field. This group name cannot be the same as the name of another group in the same level, and you cannot use "LUN SCAN" as a group name. The group name can contain spaces and is not case-sensitive. The group name can be a maximum of 50 bytes. You can use the following characters: A-Z a-z 0-9 - _ . @ The group name may include spaces, but cannot consist only of spaces. Leading or trailing spaces are discarded. 5. From the Icon drop-down list, select the icon you want to assign to the logical group being created. 6. Review the information displayed in the Create Group window. If the information is correct, click OK button to create the specified new logical group. If it is not correct, click Cancel button to cancel your request.
7-4 Viewing and editing logical group properties

Users with Modify permission can edit the logical group properties. To view and edit the logical group properties: 1. In the Explorer menu, select My Groups and then Logical Groups. 2. Expand the tree in the navigation area as necessary and then in the navigation area, select the logical group you want to view or edit. 3. In the application bar area, click the Modify Properties button.
107
Performing logical group operations The Modify Properties window appears (see Figure 7-2).
Figure 7-2 Modifying properties 4. Edit the properties of the logical group (parent group, group name, icon) as necessary. NOTE: Regarding Changing the Name: You cannot use "LUN SCAN" as a group name, and you cannot have two groups with the same name on the same level. The group name can contain spaces and is not case-sensitive. For example, if "GROUP 1" already exists at the same level as the selected logical group, you cannot use the name "GROUP 1" or "group 1". The group name can be a maximum of 50 bytes. You can use the following characters: A-Z a-z 0-9 - _ . @ The group name may include spaces, but cannot consist only of spaces. Leading or trailing spaces are discarded. NOTE: If you have moved a logical group to within another logical group by changing the parent group, the following changes will be applied: When a logical group above the group being moved is assigned to a resource group, the logical group
being moved and the logical groups within are removed from the resource group to which the higherlevel logical group is assigned.
When a move destination logical group is assigned to a resource group, the logical group being moved
and the logical groups within are added to the resource group to which the move destination logical group is assigned.
See section 6-3 for further information on resource group operations. 5. Click OK button to save your changes (if any) to the group properties and close the window, or click Cancel button to close the window without saving changes.
7-5 Deleting a logical group

Users with Modify permission can delete a logical group. NOTE: For instructions on how to delete a storage group that contains LUNs or a parent group that contains one or more storage groups, see section 7-6-6 . NOTE: You cannot, however, delete a logical group that is assigned to a resource group. To delete such a logical group, you must first delete the corresponding resource group. 108
To delete a logical group from Device Manager: 1. In the Explorer menu, select My Groups and then Logical Groups. 2. Expand the tree in the navigation area as necessary and then in the navigation area, select the group that you want to delete. 3. In the application bar area, click the Delete Group button. Device Manager displays your request to remove a logical group, and asks you to confirm it. If the group you are deleting contains any subgroups, Device Manager lists the groups and asks you to confirm your request. 4. Click OK button to delete the logical group and its subgroups (if any) or click Cancel button to cancel your request.
7-6 Storage group operations

Users with Modify permission can manage storage groups. Users with View permission can only view the storage group information. A Device Manager storage group is a user-defined set of LUNs that can be manipulated as a group. When you view the contents of a storage group, you can view property information on the selected storage group and information on the LDEVs managed under that storage group. You can add, remove, and move storage in a storage group, and you can change the security properties of a storage group. Device Manager storage group operations include:
Viewing the contents of a storage group (see section 7-6-1 ) Assigning a path and adding storage to a storage group (see section 7-6-2 ) Moving storage from one group to another (see section 7-6-3 ) Modifying LUN security for a group (see section 7-6-4 ) Removing storage from a group (see section 7-6-5 ) Deleting a storage group (see section 7-6-6 )
For instructions on creating storage groups, see section 7-3 . NOTE: When an error occurs during a storage group operation, the Device Manager might ask you to perform the Refresh operation. If you do not have Refresh privileges, ask a user with Modify permission, who is assigned the All Resources resource group, to perform the Refresh operation.
7-6-1 Viewing the contents of a storage group

When you view the contents of a storage group, you can view property information on the selected storage group and information about the LDEVs managed under that storage group. To view the contents of a storage group: 1. In the Explorer menu, select My Groups and then Logical Groups, and expand the tree in the navigation area as necessary 2. In the navigation area, select the desired storage group (see Figure 7-3).
109
Figure 7-3 Viewing the contents of a storage group The application bar area displays the operation buttons that can be used for the selected storage group.
Modify properties (see section 7-4 ) Delete group (see section 7-6-6 )
The application area displays the following information and operation buttons for the storage in the selected storage group:
Logical group information: Name and icon, parent group, number of LUNs, configured
capacity, storage subsystem, and list of LDEVs in the storage group (see step 3)
Add like storage button (see section 7-6-2 ) Add storage button (see section 7-6-2 ) Remove storage button (see section 7-6-5 ) Move storage button (see section 7-6-3 ) Modify security button (see section 7-6-4 )
3. To view detailed information for an LDEV in the storage group, select the LDEV to open the Detailed InformationLDEV-number window. Table 7-1 describes the following information displayed on the Detailed InformationLDEV-number window.
110
Performing logical group operations Table 7-1 LDEV-number window detailed information Item
Detailed Information LDEV
Description
Displays the logical device number. For the LUSE volume, the LDEV numbers of logical devices that make up the LUSE volume are displayed in the dropdown list. Displays the LDEV type. This item is displayed only for XP24000/XP20000 and XP12000/XP10000/SVS200. Displays the array control processor. Displays the array group number. Displays the RAID level. Displays the LDEV capacity information. Displays the LDEV capacity information. When the volume attribute of the LDEV is THP-VOL, the physical capacity of the data storage area allocated from a THP pool is displayed. When the volume attribute of the LDEV is not THP-VOL, the same value as Capacity is displayed. When the value cannot be identified, n/a is displayed. This item is displayed only for XP24000/XP20000. The number of blocks that make up the LDEV is displayed. For a LUSE volume, the total number of blocks in the LDEVs that make up the LUSE volume is displayed. Displays the value that has been set as the threshold for the THP volume. This item is displayed only for XP24000/XP20000. Displays the status of the LDEV. For a LUSE volume, the statuses of all the LDEVs that make up the volume are displayed. This item is displayed only for XP24000/XP20000 and XP12000/XP10000/SVS200. Displays the emulation type (StorageWorks XP Disk Array;emulation-type x number-of-LDEVs is shown for a LUSE volume). Displays the copy type: XP Business Copy Software, XP Continuous Access Software, XP Snapshot, or XP Continuous Access Journal Software. Displays the volume attribute. Displays the command device status.
Type ACP Array Group RAID Level Capacity Consumed Capacity
Block
Threshold Status
EMU Type Copy Type Volume Attr CMD DEV Mainframe Volume Information
Displays information about mainframe volumes. This item is displayed only for a mainframe volume. VOLSER DEVN Displays the volume serial number of the logical device. A blank appears if the serial number cannot be obtained. Displays all the device numbers set for the logical device. A blank appears if the device numbers cannot be obtained.
111
Path Information LDEV Port/Port Type/HSD/LU N Port/LUN Port SLPR WWN/iSCSI Name Nickname Group Host File System
Description
Displays the logical device number. Displays the port name, port type, host storage domain (HSD) nickname, and logical unit number. The host storage domain (HSD) is displayed only for XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128. Displays the port name and logical unit number. These items are displayed only for XP512/XP48. Displays the SLPR number of the port. This item is displayed only for a storage subsystem that can use XP Disk/Cache Partition. Displays the nickname corresponding to the WWN or iSCSI name displayed in Host. If no nickname has been set, nothing is displayed. Displays the name of the storage group to which the path belongs. Displays the host name and the WWN. If the host name cannot be acquired, n/a is displayed. Displays the mount point on the host. The value is displayed only when a Device Manager agent is installed on the host. A maximum of 378 bytes is used to display the mount point. Displays SCSI information recognized by the host. Displays the volume capacity. Displays the percentage of volume usage. The unit is %. For details about how to calculate the percentage and details about the conditions that prevent this item from being displayed, see the description of % Used in section 8-2-1 . When multiple paths are assigned to a volume, the following information is displayed:
Host Bus/TID/LUN Capacity % Used
When paths are assigned to multiple hosts

The percentage of volume usage on a host to which the Device Manager agent last sent the data is displayed. If the percentage of volume usage cannot be calculated on that host, dashes (--) appear even when the volume is being used by another host.
When multiple paths are assigned to a single host

The largest value is displayed as the percentage of storage usage. Last Updated Displays the date and time when the Device Manager agent performed the last update. If multiple paths are assigned to the volume, the date and time when information was last updated on a host to which Device Manager agent last sent the data is displayed.
112
THP Pool Information
Description
Displays information about the THP pool. If the volume attribute of the LDEV is THP-VOL, a pool ID for the associated THP pool is displayed. If the volume attribute is THP-Pool-VOL, a pool ID for the registered THP pool is displayed. Other than these cases, or when the volume attribute is THP-VOL and the volume is not associated with the THP pool, No THP Pool Information Found. is displayed. This item is displayed only for XP24000/XP20000. Pool ID Capacity Displays the Pool ID of the THP pool. Displays the capacity of the THP pool.
Free Capacity Displays the capacity that is obtained by subtracting the consumed capacity of the THP volumes from the capacity of the THP pool. %Used Threshold1 Threshold2 Number of THP Pool VOLs Number of THP VOLs Capacity of THP VOLs Status Displays the percentage of consumed capacity of the THP volumes in the THP pool. The unit is %. Displays the value that has been set by the user as the threshold for the THP pool usage rate (%). Displays the fixed value that has been set as the threshold for the THP pool usage rate (%). Displays the number of THP pool volumes that have been registered in the THP pool. Displays the number of THP volumes that have been assigned to the THP pool. Displays the total capacity of the THP volumes that have been assigned to the THP pool. Displays one of the following values as the THP pool usage status:
Normal = The THP pool usage rate has not reached threshold 1 or
threshold 2.
Over Threshold = The THP pool usage rate has exceeded threshold
1 or threshold 2, or both.
Blocked = The THP pool usage rate has reached 100%, or a failure
has occurred. CLPR Displays the CLPR number of the THP pool.
113
Pair Information
Description
Displays pair information. This item is not displayed if the volume attribute of the LDEV is POOL. Copy Type Copy Status Fence Level Split Time Displays the copy type: XP Business Copy Software, XP Continuous Access Software, XP Snapshot, or XP Continuous Access Journal Software. Displays the copy status when volumes are paired. Displays the recovery settings used when a failure occurs during execution of XP Continuous Access Software. Displays the time when a snapshot is obtained if Copy Type is XP Snapshot. A blank is displayed if Copy Type is not XP Snapshot. This item is displayed only for XP24000/XP20000 and XP12000/XP10000/SVS200. Displays P-VOL information. LDEV Displays the logical device number of the primary volume.
P-VOL
Journal Group For XP Continuous Access Journal Software, displays the number of the journal group to which the primary volume belongs. In all other cases, this item is blank. This item is displayed when the displayed pair contains an XP Continuous Access Journal Software pair. Type Serial No. Array Group S-VOL Displays the model name of the storage subsystem to which the primary volume belongs. Displays the serial number of the storage subsystem to which the primary volume belongs. Displays the number of the array group to which the primary volume belongs.
Displays S-VOL information. LDEV Displays the logical device number of the secondary volume.
Journal Group For XP Continuous Access Journal Software, displays the number of the journal group to which the secondary volume belongs. In all other cases, this item is blank. This item is displayed when the displayed pair contains an XP Continuous Access Journal Software pair. Type Serial No. Array Group POOL Information Guard Mode Information Displays the model name of the storage subsystem to which the secondary volume belongs. Displays the serial number of the storage subsystem to which the secondary volume belongs. Displays the number of the array group to which the secondary volume belongs.
Displays POOL information. This item is displayed only if the attribute of the LDEV is POOL. POOL ID Displays the POOL ID.
Displays XP Data Retention Utility information. This item is not displayed for mainframe volumes. Attribute S-VOL Mode Displays the attribute of the logical device. Displays the S-VOL Disable attribute. Displays the INH bit attribute.
114
Virtual Partition Information
Description
Displays information about the SLPR and CLPR. This item is only displayed for a storage subsystem that can use XP Disk/Cache Partition. LDEV SLPR CLPR Displays the LDEV number. Displays the SLPR number. Displays the CLPR number.
External Subsystem Information
If an internal volume of a storage subsystem that uses XP External Storage Software is selected, this item displays the information about the external volume mapped to that internal volume. If an external volume is selected, this item displays information on the internal volume to which the external volume is mapped. If neither case applies, the message No External Storage Information found displays. External Volume(s); substance of this volume Displays information on the external volume mapped to that internal volume. This information is displayed only if an internal volume of a storage subsystem that uses XP External Storage Software is selected. For a LUSE, multiple lines will be displayed. LDEV External Subsystem Displays the LDEV number. Displays the name of the external subsystem.
External LDEV Displays the LDEV number of the external subsystem. External Subsystem Vendor Assigned Volume(s); use of this volume Displays the name of the external subsystem vendor.
Displays information on the internal volume to which the external volume is mapped. This information is displayed only if an external volume is selected. If the internal volume to which an external volume is mapped is sliced (CVS), multiple lines will be displayed. Assigned Subsystem Assigned LDEV Displays the storage subsystem name of the internal volume to which an external volume is mapped. Displays the LDEV numbers of the internal volume to which an external volume is mapped.
7-6-2 Assigning a path and adding storage to a storage group

In Device Manager, a logical device in a storage subsystem can be allocated to a LUN on a port in the storage subsystem to enable the logical device to be accessed by hosts (this operation is called adding storage). Users with the Modify permission can allocate a LUN to a logical device, and add storage to an empty group or storage group. Users with Modify permission can assign a path to a logical device and add storage to an empty group or storage group. When you add storage, you add one or more LUNs (access paths) to an empty group or a storage group. You can add storage to an Open-Allocated or to an Open-Unallocated group, or to both. During this process, you have the option of creating LUSE volumes and setting LUN security.
115
NOTE: The maximum number of LUNs that can be assigned in one operation is 100. If you attempt to assign more than 100 LUNs at one time, an error message appears. To assign more than 100 LUNs, add storage in multiple operations, adding no more than 100 LUNs in each operation. CAUTION: In the web client, increasing the amount of data that is displayed in the window increases the amount of memory that is used. To avoid a memory shortage, we recommend that you do not add more than 1,000 LUNs (access paths) to a storage group. NOTE: If an error occurs when you attempt to add storage, depending on the state of the storage, you may no longer be able to recognize the storage. If this happens, refresh the storage subsystem, and then move the affected storage to an appropriate storage group. If you do not have permissions to perform a refresh, ask a user with Modify permission, who is assigned the All Resources resource group, to perform a refresh. NOTE: A path cannot be assigned to an LDEV whose volume attribute is POOL, OnDemand, Migration-reserved, JNL-VOL, MF-JNL, THP-Pool-VOL, or System Disk. IMPORTANT: You can also assign a path to an LDEV from an All Storage (or My Storage) object. In addition, you can also add storage to an empty group or storage group from the Hosts object. To assign a path to a logical device, or to add storage to an empty group or storage group: 1. In the Explorer menu, select My Groups and then Logical Groups, and expand the tree in the navigation area as necessary. 2. In the navigation area, select the empty group or storage group to which you want to add storage. The logical-group-name subwindow is displayed in the application area. 3. In the application area, perform one of the following operations:
To add a path that has the same port and LUN security settings as the path set for a
storage subsystem: In the sortable table, select storage of which you want to inherit the port and LUN security settings. You can select no more than 16 paths at a time. Clicking the Add Like Storage button displays the Add Storage (STEP: Allocate Storage) dialog box. Perform steps 8, 9, 11, and 12.
To add storage with a new path for the LDEV:

Click the Add Storage button. If the storage group you selected in step 2 for the additional storage is empty or if the paths in the storage group have different LUN security settings, the Add Storage (STEP: Define Host/Port Connections) dialog box is displayed. Go to step 6. If all the paths in the selected storage group have the same LUN security settings and all the LDEVs are set with paths to the same port, the Add Storagelogical-group-name dialog box appears (see Figure 7-4). Proceed to step 4.
116
Figure 7-4 Adding storageselecting the storage addition operation 4. In the Add Storagelogical-group-name dialog box, select a method for adding the storage and then click the OK button. The available methods for adding storage are as follows:
Storage is added with the same port and the same security. (Only LDEV and LUN are
specified): When adding storage using the same ports and LUN security settings, you simply inherit the existing settings for the ports and LUN security settings, and assign only the LDEVs and LUNs. Select this method when you want to increase capacity while creating logical groups on a per-host basis without changing the ports and LUN security settings. To select this method, perform steps 8, 9, 11, and 12.
Storage is added to another port with the same LDEV and the same security (only a port
and LUN are specified): To add storage to other ports using the same LDEVs and LUN security settings, you simply assign ports and LUNs to the same LDEVs. Select this method when you want to configure switchover paths for existing LUNs. To select this method, perform steps 5, 7, 11, and 12. Do not select this method when using the XP512/XP48 series and selecting a LUN group in the Assign LUN(s) window (see Figure 7-13).
The usual storage addition (all parameters are specified): Select this method when you
wish to add storage using the normal procedure. To select this method, perform steps 6, 7, 8, 9, 10, 11, and 12. 5. STEP: Select Ports. The Select Ports window (see Figure 7-5) enables you to select the desired port(s) for the storage to be added. Note that you cannot select the port already set for the path in the storage group to which storage is to be added, or a port whose type is different from the set port. For the XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, clicking the Detail button displayed in the column of each port enables you to check security information for the port. For a Fibre Channel port, when all WWNs that are set to the storage group path for LUN security do not exist in the host storage domain, a new host storage domain is automatically created, and the Edit New HSD button is displayed. To edit the created host storage domain information, click the Edit New HSD button, and then go to step 7. To use the host storage domain for LUN security without editing its default information, click the Next button, and then go to step 11. When there is a host storage domain whose set WWNs exactly match the
117
Performing logical group operations WWNs set to the storage group path for LUN security, that host storage domain is used as LUN security. Click the Next button, and then go to step 11.
Figure 7-5 Adding storageselecting ports
NOTE: You can only select ports whose type is Fibre. The check boxes for the other types of ports are disabled and cannot be selected. NOTE: When the port is recognized as an Initiator port or an external port, the Port check box appears inactive and cannot be selected. For details about Initiator ports, see the XP Continuous Access Software documentation for the desired storage subsystem. NOTE: In a storage subsystem that is using XP Disk/Cache Partition, ports that are recognized as an Initiator port, external port, or RCU Target port belong to SLPR0. These ports are displayed even if the storage subsystem has been added by using a user ID other than the user ID of the partitioned storage administrator for SLPR0. In such a case, however, an attempt to set a path to RCU Target fails, and the path cannot be set. NOTE: For XP1024/XP128, the following ports are not displayed: CL1-S, CL1-T, CL1-U, CL1-V, CL1-W, CL1-X, CL1-Y, CL1-Z, CL2-S, CL2-T, CL2-U, CL2-V, CL2-W, CL2-X, CL2-Y, CL2-Z. NOTE: For XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, if security is set for the storage group, you can only select either the ports that contain an HSD assigned with a WWN that has exactly the same security settings as the HSD; or the ports assigned with a WWN that has the specified security settings and is not being used by a HSD. When security is not set, you can select ports that have not been set for a storage group. 6. STEP: Define Host/Port Connections. The Define Host/Port Connections window (see Figure 7-6) enables you to define the combination of port(s) and host WWN. You can also select only the port assigned to the storage without defining the port-host combination.
118
Figure 7-6 Adding storagedefining host/port connections Perform the following operations on the Add Storage (Step: Define Host/Port Connections) window:
Select a storage subsystem When adding storage to an empty group, you can select the desired storage subsystem. If you are adding storage to the existing storage group, the storage subsystem to which the LDEV belongs is displayed.
Select hosts (WWN) Select the WWNs to be set as LUN security for the storage you are adding. This specification is optional. In the Host: WWN/iSCSI Name section, if you opened the Add Storage (Step: Define Host/Port Connections) window from the Logical Groups object or All Storage (or My Storage) object, all the hosts and their WWNs and iSCSI names that are recognized by Device Manager are displayed. If you have started the window from the Hosts object, the hosts in the navigation area that were selected and their WWNs or iSCSI names are displayed.
Select ports For XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, clicking the Detail button displayed in the column of each port enables you to check security information for the port.
NOTE: You can only select ports whose type is Fibre. The check boxes for the other types of ports are disabled and cannot be selected. NOTE: When the port is recognized as an Initiator port or an external port, the Port check box is disabled and cannot be selected. For details about Initiator ports, see the XP Continuous Access Software manual for the desired storage subsystem. NOTE: In a storage subsystem that is using XP Disk/Cache Partition Manager, ports that are recognized as an Initiator port, external port, or RCU Target port belong to SLPR0. These ports are displayed even if the storage subsystem has been added by using a user ID other than the user ID of the partitioned storage administrator for SLPR0. In such a case, however, an attempt to set a path to RCU Target fails, and the path cannot be set. NOTE: For XP1024/XP128, the following ports are not displayed: CL1-S, CL1-T, CL1-U, CL1-V, CL1-W, CL1-X, CL1-Y, CL1-Z, CL2-S, CL2-T, CL2-U, CL2-V, CL2-W, CL2-X, CL2-Y, CL2-Z
119
Define the combination of hosts and ports After you choose the hosts and the ports, and then click the Add button, the combination of the hosts and ports are added to the Defined Host/Port Connections section. If security (WWN) was initially selected, then in Port, click View Available Port. Only the available ports are displayed for activation, so select the desired port. If port was initially selected from Port, then in Host: WWN/iSCSI Name click View Available Host: WWN/iSCSI Name. Only the available securities are displayed for activation, so select the desired security. Note that for XP24000/XP20000, XP12000/XP10000/SVS200, XP1024/XP128, if multiple ports are selected initially, an unusable security setting might appear available even after you click View Available Host: WWN/iSCSI Name in Host: WWN/iSCSI Name. In such a case, select security so that each selected port satisfies one of the following conditions. If you select security that does not satisfy the conditions, an error occurs when the Add button is selected.
WWNs that exactly match the WWNs set in the host storage domains on the selected
port
WWNs that are not used in the host storage domains on the selected port
For XP512/XP48, you can also set a WWN group as LUN security. To remove a defined host-port combination, select the target host-port combination in the Defined Host/Port Connections section, and then click the Remove button. NOTE: You will be able to assign each LUN to different host/port connections, so make sure to define all desired host/port connections.
Set a host storage domain In the Defined Host/Port Connections section, ports to be assigned to the storage or the combinations of hosts and ports are displayed. A Fibre Channel port of XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128 has its own host storage domain with WWNs specified. A WWN can only be set in one host storage domain on each port. For Fibre Channel ports, if all the selected WWNs are not used in the host storage domains, a new host storage domain is created automatically. In this case, the Edit New HSD button is displayed. To edit information of the created host storage domain, click the Edit New HSD button, and then go to step 7. If you use the created storage domain as LUN security without editing its default information, click the Next button, and then go to step 8. If there is a host storage domain whose set WWNs exactly match the selected WWNs, that host storage domain is used as LUN security. If you have only selected ports and not hosts, an existing host storage domain for which no WWN has been specified is used as LUN security. Click the Next button, and then go to step 8.
7. In the Host Storage Domain Info dialog box (see Figure 7-7), you can edit the newly created information about host storage domains. When you click the OK button, the edited information is stored as HSD information and the dialog box closes. When you return to the Define Host/Port Connections window, the HSD name displayed in the Defined Host/Port Connections section is changed to a new name. When you select the Cancel button, the edited information is discarded. If you have started the Host Storage Domain Info dialog box from the Define Host/Port Connections window, go to step 8. If you have started the Host Storage Domain Info dialog box from the Select Ports window, go to step 11. NOTE: When you close the Host Storage Domain Info dialog box by clicking the OK button, nothing is confirmed as HSD information yet. Therefore, if you click the Detail button to display the HSD information for a desired port, the edited HSD name is not displayed.
120
Figure 7-7 Host Storage Domain Info 8. Allocate Storage Step. The Allocate Storage window (see Figure 7-8) enables you to enter the ID(s) of the LDEV(s) that you want to add in any of the following three ways. This step is not displayed if the storage subsystem is started from the Open-Allocated or Open-Unallocated group in the All Storage object.
Figure 7-8 Adding storageallocating storage
Enter LDEVs: Enter the desired LDEV(s), and click the Next button. To specify multiple
LDEVs, use a comma as the delimiter between LDEVs.
Browse LDEVs: A list of LDEVs in the selected storage subsystem is displayed (see
Figure 7-9). For the XP512/XP48, the LDEVs whose paths are assigned to all the ports in the device are not displayed. For the XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, all LDEVs are displayed. Clicking the link of an LDEV number 121
Performing logical group operations displays the detailed information for each LDEV. Select the desired LDEV(s), and click the Next button.
Figure 7-9 Adding storagebrowsing for LDEVs
Find Storage: Specify a condition, and then find the storage. You must specify one of the
following: total capacity or the storage count. If you specify total capacity, you can omit the emulation type. If necessary, you can also specify the RAID level, LDEV type, disk size (GB), and ACP number. If you specify a condition in Find Storage, and then click Next, the Storage Found dialog box appears. This dialog box displays a maximum of 300 storage devices that have been found (see Figure 7-10). The displayed list does not include volumes to which paths have been assigned or internal volumes to which external volumes are mapped. To allocate such volumes, select Enter LDEVs or Browse LDEVs. Click the Next button to continue, or click the Back button to go back to the Allocate Storage window.
122
Figure 7-10 Adding storagestorage found 9. Define LUs step (optional). The Define LUs window (Figure 7-11) enables you to create LUSE volumes. If you do not want to create LUSE volumes, click the Next button to continue. This step is not displayed in the following cases:
When storage is allocated from the Open-Allocated group in the All Storage object When only one LDEV is selected in the above Allocate Storage step
To create LUSE volumes from unallocated LDEVs, select the desired LDEVs for each LUSE volume, and select the Create LUSE button. See section 8-6 for LUSE volume requirements. When the LUSE information is correct, click the Next button to continue. NOTE: Regarding representative LDEV number for a LUSE volume: For the StorageWorks XP Disk Array, the smallest number among the LDEVs used to configure the LUSE volume is selected automatically as the representative LDEV for the new LUSE volume. NOTE: For a storage subsystem that is using XP Disk/Cache Partition, do not create LUSE volumes by using LDEVs with different SLPRs and CLPRs. If SLPRs differ, the partitioned storage administrator cannot manage the storage subsystem. If CLPRs differ, the effect of cache partitioning might decrease.
123
Figure 7-11 Adding storagedefining LUs 10. Assign Host/Port Connections Step. The Assign Host/Port Connections window enables you to set the association between the volume path and an LDEV (see Figure 7-12). The host/port connection(s) that you selected on the Define Host/Port Connection window are displayed. Select the desired LDEV/LU(s) and host/port connection(s). To select a LU first, click the View Available Port-Host: WWN/iSCSI Name link to display the available ports and their WWNs, and then select Port-Host: WWN/iSCSI Name. When you select Port-Host: WWN/iSCSI Name first, click the View Available LU link to display the available LUs and then select LU. When these selections are completed, click Add. Repeat as necessary. When you are finished assigning connections, click the Next button to continue. NOTE: For a storage subsystem that is using XP Disk/Cache Partition, do not associate LDEVs and ports that belong to different SLPRs. If SLPRs differ, the partitioned storage administrator can no longer manage the storage subsystem.
124
Figure 7-12 Adding storageassigning host/port connection 11. Assign LUNs Step. The Assign LUN(s) window (see Figure 7-13) enables you to select the desired LUNs for the storage being added. The LDEVs/LUs and host/port connections that you selected on the Assign Host/Port Connections window are displayed. Use one of the following methods to assign LUNs to LDEVs:
Assigning preselected LUNs

By default, the LUNS that can be selected are assigned in ascending order beginning with the smallest LUN.
Assigning desired LUNs

From the drop-down list, select the LUN of the LDEV (the smallest numbered LDEV) flagged with an asterisk (*) as the start number. Clicking Auto Number assigns LUNs in ascending order beginning with this start number.
Assigning LUNs individually

From the drop-down list, assign the desired LUNs. When you are done assigning LUNs, select Finish. If any of the following conditions apply, Finish is inactive:
A LUN is already assigned to a path for the same port or host storage domain. The number of LUNs assigned to the same port or host storage domain exceeds the
maximum number.
If LUNs are assigned in ascending order using the desired LUN as the start number, the
total number of LUNs whose numbers are greater than the start number is less than the number of LDEVs. NOTE: For XP512/XP48: If you set only ports in the Define Host/Port Connections window (Define Host/Port Connections Step), you can register the LUN into a LUN group at the same time you assign the LUN. To register a LUN into a LUN group, select the target LUN group. Select Unregistered if you do not want to register the LUN into a LUN group.
125
Figure 7-13 Adding storageassigning LUNs 12. Summary of Changes Step. The Summary of Changes window (see Figure 7-14) displays the requested add storage operations and asks you to confirm the requested operations. Click the Confirm button to add the storage as specified, or click the Cancel button to cancel your request to add storage. If you need to make any changes, click the Back button to return to the previous window(s). For the XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, when you click the Confirm button, a new host storage domain (HSD) is created for the port that satisfies both of the following conditions:
New host storage domain information is generated when storage is added. A path for an LU is set in the Assign Host/Port Connections window.
If an HSD with the same security settings is already generated for the port, an error message appears and you cannot add storage. If your attempt to add storage fails, an error message is displayed. You can re-execute the operation by clicking the Back button to return to the Summary of Changes window.
126
Figure 7-14 Adding storageconfirmation
7-6-3 Moving storage from one group to another

Users with Modify permission can move storage (LUNs) from one storage group to another. When you move storage, the selected LUN (path) is moved to another storage group or to an empty group. When moving storage to another storage group, the target must be a storage group that is assigned a LUN within the same storage subsystem as the LUN that is being moved. The access paths to the LUs are not affected by this operation. NOTE: For details on how to create a new logical group, see section 7-3 . To move one or more LUNs (paths) from one storage group to another: 1. Select an object to move storage from. You can move storage from any of the following objects:
To move storage from the Logical Groups object:

In the Explorer menu, select My Groups and then Logical Groups, expand the Logical Groups object tree in the navigation area, and then select a storage group that contains the LUN that you want to move. The logical-group-name subwindow is displayed in the application area.
To move storage from the Hosts object:

In the Explorer menu, select Resources and then Hosts, expand the Hosts object tree in the navigation area, and then select the host associated with the storage group that contains the LUN that you want to move. The host-name subwindow is displayed in the application area.
To move storage from the All Storage or My Storage object:

In the Explorer menu, select Resources and then All Storage or My Storage, expand the object tree in the navigation area, and then select an Open-Allocated group in the storage subsystem that contains the LUN that you want to move. The Open-Allocated subwindow is displayed in the application area. When moving storage from the Open-Allocated subwindow, you can also register a LUN that is not assigned to a storage group to a logical group. 127
Performing logical group operations 2. In the application area, select the LDEVs that contain the LUN you want to move. In one operation, you can select a maximum of 100 LDEVs. If you want to perform an operation on more than 100 LDEVs, perform the operation multiple times, selecting no more than 100 LDEVs in each operation. Click the Move Storage button to move storage from the logical-group-name subwindow or the host-name subwindow. Click the Move to Group button to move storage from the OpenAllocated subwindow. NOTE: When moving a LUN from the host-name subwindow, you cannot simultaneously select LUNs from different storage subsystems. 3. After moving storage from the Open-Allocated subwindow, if you have selected an LDEV that has multiple volume paths, the Select Paths window is displayed (see Figure 7-15). Select the desired path(s) to be registered to the target storage group, and then click the OK button.
Figure 7-15 Moving storageselecting the path(s) 4. In the Select Logical Group window (see Figure 7-16), select the desired target storage group, and click the OK button to continue. An empty group, or a storage group that is assigned a LUN that is in the same storage subsystem as the selected LUN, can be specified.
128
Figure 7-16 Moving storageselecting the target storage group 5. When the confirmation window displays, click OK to move the LUN(s) as specified, or click Cancel to cancel your request to move the LUN(s). If you move storage from Logical Groups or Hosts objects, the Move StorageConfirmation window displays. If you move storage from the Open-Allocated group, the Move to GroupConfirmation window displays. CAUTION: If an error occurs while you are moving storage (LUN) to another storage group, the same LUN may exist in both the source and target storage groups at the same time. In this case, delete the duplicate LUN from the source storage group. Do not release the LUN when you delete the LUN.
7-6-4 Modifying LUN security for a group

Users with Modify permission can modify the LUN security of the LUN(s) in a storage group. LUN security is a function that limits the hosts (WWNs) that can access each LUN by setting host WWNs to each LUN in a storage group. For XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, host WWNs that are set as security for LUNs in a storage group make up a host storage domain on a storage subsystem Fibre Channel port. To modify the LUN security, the XP LUN Manager feature must be enabled. To modify the LUN security of one or more LUNs: 1. In the Explorer menu, select My Groups and then Logical Groups, and expand the tree in the navigation area as necessary. 2. In the navigation area, select the storage group for which you want to modify LUN security. 3. In the application area, select the desired LUN(s) and then click the Modify Security button to start the Modify Security wizard. Select the LDEV to which a path has been assigned from the port of the same connection type. In one operation, you can select a maximum of 100 LUNs. If you want to perform an operation on more than 100 LUNs, perform the operation multiple times, selecting no more than 100 LUNs in each operation. 129
Performing logical group operations 4. Select Hosts Step. The Select Hosts window (see Figure 7-17) displays the hosts whose security can be set. Check boxes are preselected on the hosts that have already been granted access permissions for the selected LUN. Select the check boxes for the hosts that you want to grant access permissions for the LUN. If you clear a check box, access permissions to the LUN for that host are revoked. After you select the hosts to grant access permissions, click on Next to go to the next step.
Figure 7-17 Modifying securityStep 1: Select Hosts 5. Select WWNs/iSCSI Names Step. The Select WWNs window (see Figure 7-18) displays the WWN(s) for the selected host(s) and enables you to select the WWN(s) that you want to secure to the LUN(s). In this window, select the desired security properties of the WWN(s), and then click the Next button. The security property that can be set depends on the selected paths and the status of the WWNs.
a. If the selected WWNs are not assigned to all of the selected paths, the following security
properties can be set:
Not assigned (Current Status) Assign this security to all selected paths
b. If the selected WWNs are assigned to all of the selected paths, the following security
properties can be set:
Assigned to all paths (Current Status) Delete this security from all selected paths
c. If the selected WWNs are assigned to only some of the selected paths, the following
security properties can be set:
Assigned to some paths (Current Status) Assign this security to all selected paths Delete this security from all selected paths
d. If the selected WWNs belong to the HSDs assigned to one of the selected paths or belong
to the HSDs that do not contain the selected paths, you cannot set security. In this case, Not assigned (Current Status) is displayed in the inactive state. Clicking the Next button might display the following warning messages depending, on the storage subsystem to which the selected storage belongs.
130
Warning concerning host storage domains

With XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, if you modify security for storage that belongs to a host storage domain, security for all storage belonging to that host storage domain changes. For this reason, Device Manager lists all LDEVs that will be affected by your requested LUN security change (see Figure 7-19). Check the warning message carefully, and then click the Next button to continue, or the Back button to return to the previous window(s).
Figure 7-18 Modifying securityStep 2: Select WWNs
Figure 7-19 Modifying securitywarning 6. Summary of Changes Step. The Summary of Changes window displays the requested LUN security changes and asks you to confirm the requested operations. Click Confirm to modify 131
Performing logical group operations the LUN security as specified, or click Cancel to cancel your request. If you need to make any changes, click Back to return to the previous window (s). CAUTION: If you change or remove the LUN security set for an external volume, the internal volume to which that external volume is mapped might become unavailable. In this case, a warning message is displayed. For details on messages, see section 12-3-7 . If your attempt to modify LUN security fails, an error message is displayed. You can re-execute the operation by clicking the Back button to return to the Summary of Changes window.
7-6-5 Removing storage from a group

Users with Modify permission can remove storage (LUNs) from an existing storage group. When you remove storage, you remove the selected LUN(s) from the storage group. During the remove storage operation, you can select to keep or delete the LUN(s) (access paths) themselves. NOTE: To remove paths from LDEVs, use the unallocate operation (see section 8-5 ). CAUTION: Before deleting a LUN, make sure that no access is underway from a host. When a LUN is deleted, all I/Os being executed between a host and that LUN are canceled. NOTE: For StorageWorks XP Disk Array: Even if a LUN is deleted, the storage subsystem port or HSD to which that LUN belongs is not reset. NOTE: For XP512/XP48 LUN group: When you remove storage belonging to a LUN group, you must select all storage in that LUN group. If you wish to remove only a portion of such storage, you must first remove the desired LUNs from the LUN group, and then remove the storage. To remove storage (LUNs) from a storage group: 1. You can start the remove storage operation from either the Logical Groups object or the Hosts object.
In the Explorer menu, select My Groups and then Logical Groups, expand the Logical
Groups object tree in the navigation area, and then select the storage group that contains the LUN(s) that you want to delete.
In the Explorer menu, select Resources and then Hosts, expand the Hosts object tree in
the navigation area, and then select the host associated with the storage group that contains the LUN(s) that you want to delete. 2. In the application area, select the LUN(s) to be deleted, and click the Remove Storage button. If you select an unremovable LUN, an error is displayed in the pop-up window. Restrictions on deleting LUNs:
In one operation, you can delete a maximum of 100 LUNs. If you want to delete an
operation on more than 100 LUNs, perform the operation multiple times, selecting no more than 100 LUNs in each operation.
For XP24000/XP20000, XP12000/XP10000/SVS200, and XP512/XP48, you cannot

delete the last volume path of the logical device specified as a copy pair volume.
For XP512/XP48, you cannot delete the last volume path of the logical device set as a
command device or the logical device specified as a copy pair volume. The Remove StorageConfirmation window is displayed, with a list of the LUNs you are deleting (see Figure 7-20).
132
Figure 7-20 Removing storage groupsconfirmation 3. Take one of the following actions to keep or delete the access paths to the LDEVs, as appropriate:
Select the Keep access path check box to remove the path from the storage group only.
The path itself remains allocated to the LDEV and the target LDEV remains in the OpenAllocated group.
Do not select the Keep access path check box. The path is removed from the storage
group and from the LDEV. The LDEV to which the path was set is moved to the OpenUnallocated group. CAUTION: Before deleting a path, make sure that the path is no longer in use. NOTE: For LUSE: If the LDEVs and paths to be deleted are in a LUSE volume and all paths of the LUSE volume will be deleted, Device Manager enables you to delete the LUSE volume if desired.
If you click the OK button without selecting Keep access path in the Remove StorageConfirmation window, the ConfirmationLUSE window displayed.
To delete the LUSE volume, click the Delete LUSE button. To retain the LUSE volume, click the Keep LUSE button. Restrictions for deleting access paths: For the XP512/XP48, storage (LDEVs) defined for XP Business Copy Software or XP Continuous Access Software may not have a port or LUN assigned. Device Manager cannot be used to remove storage that is incorrectly configured (lacking ports or LUNs, for example). Use the SVP console to remove such storage. 4. If you chose to delete the access paths, read the warning (under Storage List in the Remove StorageConfirmation window) about stopping I/O processing from all hosts to the specified LUN(s). 5. Select YES, I have confirmed it to confirm deletion of the specified path(s). 6. Click the OK button to delete the specified LUN(s) from the specified storage group and, if applicable, to remove the specified path(s) from the LDEVs/LUs. Click the Cancel button to cancel your request. LDEVs/LUs with no remaining paths are now listed in the Open-Unallocated group of the storage subsystem (under All Storage or My Storage in the navigation area). When an access path is deleted, the target LDEV or LU is moved to the Open-Unallocated group of the storage subsystem. The Open-Unallocated group is displayed under the All Storage or My Storage object in the navigation area.
133
Performing logical group operations If your attempt to remove storage fails, an error message is displayed. You can re-execute the operation by clicking the Back button to return to the Remove StorageConfirmation window.
7-6-6 Deleting a storage group

Users with Modify permission can delete storage groups. When a storage group is deleted, both the volume paths and the data are deleted from the storage group that is being deleted. During the remove storage groups operation, you can choose to keep or delete the LUN(s) (access paths) themselves. CAUTION: Data may be lost if LUNs are released. Before deleting a storage group, you should back up the data that is stored on the LDEVs in the storage group. In addition, you should check that you will no longer have any need to use the storage in that storage group. CAUTION: Before deleting a LUN, make sure that no access is underway from a host. When a LUN is deleted, all I/Os being executed between a host and that LUN are canceled. NOTE: For StorageWorks XP Disk Array: Even when a LUN is deleted, the storage subsystem port or HSD to which that LUN belongs is not reset. To delete a storage group or a logical group that contains a storage group: 1. In the Explorer menu, select My Groups and then Logical Groups, and expand the tree in the navigation area as necessary. 2. In the navigation area, select the storage group that you want to delete. 3. Click the Delete Group button in the application bar area. NOTE: If the selected group does not contain any storage, see section 7-5 for details on deleting a logical group. The Delete Logical GroupConfirmation window is displayed, with a list of LUNs in the group you are deleting (see Figure 7-21).
Figure 7-21 Deleting a logical groupconfirmation 4. Take one of the following actions to keep or delete the access paths to the LDEVs:
To keep the access paths to the LDEVs, select the Keep access path check box. The
storage group is deleted, but the path itself remains allocated to the LDEV and the LDEV that was contained in the deleted storage group remains in the Open-Allocated group.
134
To delete the access paths to the LDEVs, do not select the Keep access path check
box. The path is removed from all LDEVs in the group, and the LDEVs are moved to the Open-Unallocated group. CAUTION: Before deleting a path, make sure that the path is no longer in use. NOTE: For LUSE: If all paths of the LUSE volume will be deleted, Device Manager enables you to delete or keep the LUSE volume if desired. To delete a LUSE volume, in the Delete Logical GroupConfirmation window, click OK without selecting Keep access path. In the Confirmation LUSE window, click the Delete LUSE button. To retain the LUSE volume, click the Keep LUSE button, except for the XP512/XP48. For XP512/XP48, LUSE is deleted at the same time that the path is deleted. Canceling the LUSE deletion for XP512/XP48 cannot be performed. Restrictions for deleting access paths:
For XP24000/XP20000, XP12000/XP10000/SVS200, and XP1024/XP128, you cannot

delete the last volume path of a logical device specified as a copy pair volume.
For XP512/XP48, you cannot delete the last volume path of a logical device set to a
command device or a logical device specified as a copy pair volume.
For the XP512/XP48, storage (LDEVs) defined for XP Business Copy Software or XP
Continuous Access Software may not have a port or LUN assigned. Device Manager cannot be used to remove storage that is incorrectly configured, such as storage without ports or LUNs. The SVP console must be used to delete such storage. 5. If you chose to delete the access paths, read the warning (under Storage List in the Delete Logical GroupConfirmation window) about stopping I/O processing from all hosts to the specified LUN(s). 6. Select the YES, I have confirmed it button to confirm deletion of the specified path(s). CAUTION: The delete LUSE operation is destructive. Read and observe the important warning carefully, and click the OK button only if it is acceptable to lose the data on the LUSE. 7. Click the OK button to delete the specified group and, if applicable, to remove the specified path(s) from the LDEVs/LUs. Click the Cancel button to cancel your request to delete the group. You are notified when the delete group operation is complete. When an access path is deleted, the target LDEV or LU is moved to the Open-Unallocated group of the storage subsystem.
135

This chapter describes All Storage/My Storage logical group operations:
Overview of All Storage/My Storage operations (see section 8-1 ) Viewing the All Storage/My Storage group (see section 8-2 ) Performing a LUN Scan operation (see section 8-3 ) Allocating storage (see section 8-4 ) Unallocating storage (see section 8-5 ) Creating LUSE volumes (see section 8-6 ) Deleting LUSE volumes (see section 8-7 )
8-1 Overview of All Storage/My Storage operations

Either All Storage or My Storage is displayed under Resources in the Explorer menu, depending on the access range of the logged-in user. All Storage appears when a user assigned to the All Resources resource group has logged in. My Storage appears when a user assigned to a userdefined resource group has logged in. All Storage/My Storage includes all LDEVs that the logged-in user can manage organized into a group for each storage subsystem. If you add a new storage subsystem, the following groups are created in the group for the storage subsystem, and volumes in the storage subsystem are assigned to those groups:
Open-Allocated group: Open volumes that have already been allocated paths will be assigned to this group. Open-Unallocated group: Open volumes that have not been allocated paths will be assigned to this group. Open-Reserved group: Open volumes that cannot be allocated paths will be assigned to this group. Mainframe-Unspecified group: Mainframe volumes will be assigned to this group. Pools group: Pools that can be manipulated by Device Manager will be assigned to this group. This group is created only for XP24000/XP20000.
The All Storage/My Storage group and its subgroups cannot be deleted. The All Storage/My Storage group displays the storage subsystems and storage that can be accessed by the logged-in user, provides detailed information on their properties, and allows logged-in user to configure paths to LDEVs (the Open-Allocated group and Open-Unallocated group).
8-2 Viewing the All Storage/My Storage group

The All Storage/My Storage group is created automatically by Device Manager and includes all LDEVs that the logged-in user is permitted to manage. The Explorer menu displays All Storage for users assigned the All Resources resource group, or My Storage for users assigned a user-defined resource group. When the All Storage or My Storage object is selected in the navigation area, the application area displays the following.
136
Number of LDEVs: Total number of LDEVs in the All Storage or My Storage group (including all storage subsystems) Open-Allocated Capacity*: Total capacity of the LDEVs in the All Storage/My Storage group that are allocated paths on open volumes Open-Unallocated Capacity*: Total capacity of the LDEVs in the All Storage/My Storage group that are not allocated paths on open volumes Open-Reserved Capacity*: Total capacity of the LDEVs in the All Storage/My Storage group that cannot be allocated paths on open volumes Mainframe-Unspecified Capacity*: Total capacity of the mainframe volume in the All Storage/My Storage group Object List: List of storage subsystems in the All Storage/My Storage group. The list shows the name of each storage subsystem, the number of LDEVs contained, the capacity of the volumes contained in each group, and the last time the storage subsystem was refreshed.
When the All Storage/My Storage object tree is expanded, Device Manager displays in the navigation area a group for each storage subsystem available to the logged-in user. When storagesubsystem is selected in the navigation area, the application area displays the following details about the storage subsystem:
Name: Name of the storage subsystem Number of LDEVs: Total number of LDEVs/LUs in the storage subsystem Configured capacity*: Total capacity of the LDEVs/LUs in the storage subsystem Actual Capacity*: Total physical capacity of the LDEVs/LUs in the storage subsystem Last Refreshed: The last time the storage subsystem was refreshed or added to Device Manager Object List: A list showing the number of LDEVs, the total capacity, and the actual capacity for each of the Open-Allocated, Open-Unallocated, Open-Reserved, and Mainframe-Unspecified groups in the storage subsystem. For XP24000/XP20000, information about the Pools group is displayed.
When you select and expand a storage subsystem group in the All Storage/My Storage group, Device Manager displays the Open-Allocated group (see section 8-2-1 ), Open-Unallocated group (see section 8-2-2 ) and Open-Reserved group (see section 8-2-3 ), the Mainframe-Unspecified group (see section 8-2-4 ) for the selected storage subsystem. For XP24000/XP20000, the Pools group (see section 8-2-5 ) is also displayed. *The GB and TB capacity values are truncated to two decimal places. The MB capacity values are truncated to whole numbers. As a result, the capacity shown on the Device Manager window may be less than the actual capacity available.
8-2-1 Viewing the Open-Allocated group for a subsystem

When the Open-Allocated group for a storage subsystem is selected, the application bar area displays the button for executing the LUN Scan operation for the selected storage subsystem. For instructions for performing a LUN Scan operation, see section 8-3 . When the Open-Allocated group for a storage subsystem is selected, the application area displays the following information:
Name: Name of the storage subsystem Number of LDEVs: Number of LDEVs/LUs for which paths are allocated, for open volumes in the storage subsystem Configured Capacity*: Total capacity of LDEVs/LUs for which paths are allocated, for open volumes in the storage subsystem
137
Actual Capacity*: Total physical capacity of LDEVs/LUs for which paths are allocated, for open volumes in the storage subsystem
* The GB and TB capacity values are truncated to two decimal places. The MB capacity values are truncated to whole numbers. As a result, the capacity shown on the Device Manager window might be less than the actual capacity available.
Click Allocate Storage to add paths to the selected LDEV(s) (see section 8-4 ). Click Unallocate Storage to remove paths from the selected LDEV(s) (see section 8-5 ). Click Create LUSE button to create a LUSE that uses a selected LDEV as a representative LDEV (see section 8-6-2 ). This button is displayed only in XP24000/XP20000, XP12000/XP10000/SVS200, and XP1024/XP128. Click Move to Group to move the selected LDEV(s) to a storage group. The operations are the same as the operations for moving storage, see section 7-6-3 ). Sortable table lists the LDEVs/LUs in the Open-Allocated group for the storage subsystem and displays detailed information for each LDEV/LU (see Table 8-1). For details on the items displayed in the LDEV Detailed Information window, see Table 7-1.
Table 8-1 Open-Allocated group information under All Storage/My Storage Column
LDEV
Description
Displays the LDEV number. For XP LUN Expansion or LUSE, only a representative LDEV number is displayed. Select the link to display the Detailed Information window for the LDEV. This item can be filtered. You can filter by specifying a value range in the filtering conditions. Displays the host name and the WWNs names recognized by Device Manager. If the host name cannot be acquired, n/a is displayed. If there are multiple paths, multiple hosts and WWNs are displayed. If there is more than one path, information for each path is displayed. This item can be filtered. You can filter by specifying a partial match in the filtering conditions. Displays the port name. This item can be filtered. You can filter by specifying an exact match in the filtering conditions. Displays the port connection type.This item can be filtered. You can filter by specifying an exact match in the filtering conditions. Displays the host storage domain or iSCSI target. This item is displayed only for XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128. LUN group name for XP512/XP48. Not shown for any other storage subsystems. Displays the LUN. Displays the nickname corresponding to the WWN or iSCSI name displayed in Host. If a nickname has not been set for the WWN, a blank is displayed.
Host
Port Port Type HSD/iSCSI Target LUN Group LUN WWN/iSCSI Name Nickname
138
Type
Description
Displays the LDEV type. This column is displayed for XP24000/XP20000 and XP12000/XP10000/SVS200 only:
- = LDEV whose drive type is not identified This item can be filtered. You can filter by specifying a partial match in the filtering conditions. ArrayGroup Displays the following information about the array group. For XP24000/XP20000, XP12000/XP10000/SVS200, and XP1024/XP128, the value displayed is the virtual device number in the parity group. For XP512/XP48, the value displayed is the parity group number. This item can be filtered. You can filter by specifying a partial or exact match in the filtering conditions. Displays the SLPR number. This item is displayed only for a storage subsystem that can use XP Disk/Cache Partition.
#AT = The mapped external volume consists of SATA drives. #FC = The mapped external volume consists of FC drives. #SAS = The mapped external volume consists of SAS drives. #BD = The mapped external volume consists of BD drives. #- = The drive type of the mapped external volume is not identified. AT = LDEV that consists of SATA drives FC = LDEV that consists of FC drives SAS = LDEV that consists of SAS drives BD = LDEV that consists of BD drives
SLPR
0 is displayed if no SLPR is set. Inconsistent is displayed in either of the following cases:

CLPR If a LUSE is used, when different SLPRs are set for the LDEVs making up the LUSE When the SLPR of the LDEV or the LUSE differs from the SLPR of the assigned port
Displays the CLPR number. This item is displayed only for a storage subsystem that can use XP Disk/Cache Partition.
0 is displayed if no CLPR is set. Inconsistent is displayed if a LUSE is used and different SLPRs or CLPRs are set for
the LDEVs making up the LUSE.
A blank is displayed if the LDEV is an XP Snapshot V-VOL.

Group EMU Type Displays the name of the storage group to which the volume path (LUN) belongs. Displays the device emulation type for a HP StorageWorks XP disk array. For LUSE, displays emulation type and number of LDEVs in the LUSE. This item can be filtered. You can filter by specifying an exact match in the filtering conditions. Displays LDEV capacity. Values in GB and TB are truncated to two decimal places. Values in MB are truncated to whole numbers. So, the value shown here might be less than the actual capacity. This field also displays the size of an intermediate HRX volume. For more information on HRX intermediate volumes, refer to the documentation for the storage subsystem you use. This item can be filtered. You can filter by specifying a value range or exact match in the filtering conditions.
Capacity
139
Consumed Capacity
Description
Displays LDEV capacity information. When the volume attribute of the LDEV is THP-VOL, the physical capacity of the data storage area allocated from a THP pool is displayed. When the volume attribute of the LDEV is not THP-VOL, the same value as Capacity is displayed. When the value cannot be identified, n/a is displayed. This column is displayed only for XP24000/XP20000. This item can be filtered. You can filter by specifying a value range or exact match in the filtering conditions. Displays the attribute.
Volume Attr
LUSE = LUSE volume CVS = Volume created with the XP Virtual LVI/LUN (VLL) and Volume Shredder (or CVS)
function
LUSE (CVS) = LUSE volume consisting of CVS volumes THP-VOL = THP volume V-VOL = V-volume used in XP Snapshot GUARD = XP Data Retention Utility volume External = External volume IO Suppression = Volume to which an external volume is mapped, and for which the host I/O suppression mode is enabled cache mode is enabled
CacheEnable = Volume to which an external volume is mapped, and for which the I/O None = Ordinary volume
This item can be filtered. You can filter by specifying a partial match in the filtering conditions. Pool ID When the volume attribute of the LDEV is THP-VOL, the LDEV's Pool ID is displayed. When the volume attribute of the LDEV is not THP-VOL, a blank is displayed. This item is subject to filtering. You can filter by specifying an exact match in the filtering conditions.
140
External Subsystem
Description
Displays the external subsystem name. This column is displayed only for XP24000/XP20000 and XP12000/XP10000/SVS200. This item can be filtered. You can filter by specifying an exact match in the filtering conditions. external-subsystem-name = Displayed when all the following conditions are satisfied:1 The volume is an internal volume to which an external volume is mapped. Device Manager manages the external subsystem.
The external volume is allocated to the logged-in user. external-system-model#external-subsystem-serial-number = Displayed when all the following conditions are satisfied: A user assigned to the All Resources resource group is logged in. The volume is an internal volume to which an external volume is mapped. Device Manager does not manage the external subsystem.
The model is such that XP External Storage Software can acquire its serial number. external-system-model = Displayed when all the following conditions are satisfied: A user assigned to the All Resources resource group is logged in. The volume is an internal volume to which an external volume is mapped. Device Manager has not managed the external subsystem.
The model is such that XP External Storage Software cannot acquire its serial number. Unknown = Displayed when all of the following conditions are satisfied: The volume must be an internal volume to which an external volume is mapped. A user assigned a user-defined resource group is logged in.
No external volumes are assigned to the logged-in user. Blank = Displayed when the volume is a volume other than an internal volume to which an external volume is mapped. CMD DEV Copy Type Displays whether the LDEV is a command device (CMD DEV, Remote or blank). Displays the copy type: For P-VOLs paired with multiple S-VOLs, displays the copy type of each.
Blank = pair status unknown This item can be filtered. You can filter by specifying a partial match in the filtering conditions. Copy Role Copy role: P-VOL, S-VOL, or Blank = ordinary volume. For P-VOLs paired with multiple S-VOLs, the copy role of each pair is displayed. This item can be filtered. You can filter by specifying a partial match in the filtering conditions.
BC = XP Business Copy Software Cnt Ac-S = XP Continuous Access Synchronous Software Cnt Ac-A = XP Continuous Access Asynchronous Software Cnt Ac = XP Continuous Access Software with unidentifiable synchronous mode2 Snapshot = XP Snapshot Cnt Ac-J = XP Continuous Access Journal Software Unpaired = unpaired
141
Copy Status
Description
Copy status:
Blank = copy status is unknown For each P-VOL paired with multiple S-VOLs, the copy status of each pair is displayed. This item can be filtered. You can filter by specifying a partial match in the filtering conditions. File System Mount point (for example, D:\ for Windows, /mnt/RAID for Solaris). When a volume is mounted on multiple mount points, all mount points are displayed, separated by commas. A maximum of 378 bytes is used to display the mount point. If the Device Manager agent is not running on the host, this field is blank. Displays the volume usage (units: %). This item is updated when the Device Manager agent sends the volume usage to the Device Manager server. If the Device Manager agent is not running on the host, this field is blank. The Device Manager agent might not be installed or might be installed but not started. If multiple paths are allocated to a single volume, information is displayed for the number of times LUN security is configured to the paths, in the Open-Allocated subwindow. Use the following formula to obtain the storage usage: ((used-capacity-of-the-file-system-built-on-the-target-storage) / (storage-capacity)) x 100 (%) The usage cannot be calculated if the values required for calculation cannot be obtained correctly. In this case, -- appears. The conditions that enable % used to be displayed are as follows:
Simplex = SMPL status Pair = PAIR status Copying = COPY (PD), COPY (RS), COPY (SP), or COPY status Reverse-Copying = COPY (RS-R) copy status Split = PSUS or PSUS (SP) copy status Suspended = PSUE copy status Error in LUSE = PDUB copy status Suspending = Suspending status Deleting = Deleting status
% Used
When Windows is the platform of the host using the storage:

A drive letter is assigned to the LU. The LU is mounted on a directory. The LU has multiple partitions and, among the disks in the LU, drive letters are assigned to all partitioned disks and that LU is mounted on a directory. The LU or all of the LU that has multiple partitions is not under a dynamic disk configuration and is not incorporated into a volume manager (VxVM).
When Solaris is the platform of the host using the storage:

The target LU is not incorporated into a volume manager (VxVM, SVM, or SDS). The LU is mounted.
When Linux is the platform of the host using the storage:

The target LU is not incorporated into a volume manager (LVM, LVM2). The LU has multiple partitions and no partitioned disk is incorporated into a volume manager (LVM, LVM2). The LU or all of the LU that has multiple partitions is mounted.
When HP-UX or AIX is the platform of the host using the storage, % used is not
displayed.
142
Table 8-1 Open-Allocated group information under All Storage/My Storage Column Description
Last Updated Time of the last agent update. If multiple paths are allocated to the volume, information is displayed for the number of times LUN security is configured to the paths. If the Device Manager agent is not running on the host, this field is blank.
1
Even if all the conditions are met, if the microcode of a storage subsystem that uses XP External Storage Software is not supported in the connection-destination subsystem, that external subsystem name will not be displayed. In this case, if a user assigned to the All Resources resource group is logged in, external-systemmodel#external-subsystem-serial-number is displayed. If a user assigned to a user-defined resource group is logged in, Unknown is displayed. 2 Displayed when the storage subsystem containing the XP Continuous Access Software P-VOL has not been registered in Device Manager. Since Device Manager is able to obtain information about the synchronization mode, if the target storage subsystem (S-VOL) is an XP24000/XP20000, XP12000/XP10000/SVS200 or XP1024/XP128, Cnt Ac-S or Cnt AC-A is displayed in this column.
8-2-2 Viewing the Open-Unallocated group for a subsystem

When you select the Open-Unallocated group for a storage subsystem, the application area displays the following information:
Name: Name of the storage subsystem Number of LDEVs: Number of LDEVs/LUs for which paths are not allocated, for open volumes in the storage subsystem Configured Capacity*: Total capacity of LDEVs/LUs for which paths are not allocated, for open volumes in the storage subsystem Actual Capacity*: Total physical capacity of LDEVs/LUs for which paths are not allocated, for open volumes in the storage subsystem
* The GB and TB capacity values are truncated to two decimal places. The MB capacity values are truncated to whole numbers. As a result, the capacity shown on the Device Manager window might be less than the actual capacity available.
Click Allocate Storage to add paths to the selected LDEV(s) (see section 8-4 ). Click Create LUSE to use selected LDEVs to create a LUSE volume that has no path allocated (see section 8-6-3 ). Click Delete LUSE to delete LUSE volumes (see section 8-7 ).
The Sortable table in this window lists the LDEVs/LUs in the Open-Unallocated group for the storage subsystem and displays detailed information for each LDEV/LU (see Table 8-2). To view the detailed information for a specific LDEV, select the desired LDEV to open its Detailed Information window. For details on the items displayed in the LDEV Detailed Information window, see Table 7-1. Table 8-2 Open-Unallocated group information under All Storage/My Storage Column
LDEV
Description
Displays the LDEV number. For a LUSE, only a representative LDEV number is displayed. Select the link to display the Detailed Information window for the LDEV. This item can be filtered. You can filter by specifying a value range in the filtering conditions.
143
Table 8-2 Open-Unallocated group information under All Storage/My Storage Column
Capacity
Description
Displays LDEV capacity . Values in GB and TB are truncated to two decimal places. Values in MB are truncated to whole numbers. So, the value shown here might be less than the actual capacity. This field also displays the size of HRX intermediate volumes. For more information on the HRX intermediate volume, see the documentation for the storage subsystem that you are using. This item can be filtered. You can filter by specifying a value range or exact match in the filtering conditions. Displays LDEV capacity information. When the volume attribute of the LDEV is THP-VOL, the physical capacity of the data storage area allocated from a THP pool is displayed. When the volume attribute of the LDEV is not THP-VOL, the same value as Capacity is displayed. When the value cannot be identified, n/a is displayed. This column is displayed only for XP24000/XP20000. This item can be filtered. You can filter by specifying a value range or exact match in the filtering conditions. Displays the LDEV type for XP24000/XP20000 and XP12000/XP10000/SVS200 only.
Consumed Capacity
Type
- = LDEV whose drive type is not identified This item can be filtered. You can filter by specifying a partial match in the filtering conditions. ArrayGroup Displays information about the array group. For XP24000/XP20000, XP12000/XP10000/SVS200, and XP1024/XP128, the value displayed is the virtual device number in the parity group. For XP512/XP48, the value displayed is the parity group number. This item can be filtered. You can filter by specifying an exact match in the filtering conditions.
144
Volume Attr
Description
Displays volume attributes.
LUSE = XP LUN Expansion or LUSE volume CVS = Volume created with the XP Virtual LVI/LUN (VLL) and Volume Shredder (or
CVS) function
LUSE (CVS) = LUSE volume consisting of CVS volumes THP-VOL = THP volume V-VOL = V-volume used in XP Snapshot GUARD = XP Data Retention Utility volume External = External volume IO Suppression = Volume to which an external volume is mapped, and for which the host I/O suppression mode is enabled I/O cache mode is enabled
CacheEnable = Volume to which an external volume is mapped, and for which the None = Ordinary volume
This item can be filtered. You can filter by specifying a partial match in the filtering conditions. Pool ID When the volume attribute of the LDEV is THP-VOL, the LDEV's Pool ID is displayed. When the volume attribute of the LDEV is not THP-VOL, a blank is displayed. This item is displayed only in XP24000/XP20000. This item can be filtered. You can filter by specifying an exact match in the filtering conditions. Displays the SLPR number. This item is displayed only for a storage subsystem that can use XP Disk/Cache Partition.
SLPR
0 is displayed if no SLPR is set. Inconsistent is displayed if a LUSE is used and different SLPRs are set for the
LDEVs making up the LUSE. CLPR Displays the CLPR number. This item is displayed only for a storage subsystem that can use XP Disk/Cache Partition.
0 is displayed if no CLPR is set Inconsistent is displayed if a LUSE is used and different SLPRs or CLPRs are set
for the LDEVs making up the LUSE.

EMU Type Emulation type for StorageWorks XP Disk Array. For LUSE, this item indicates the emulation type and the number of LDEVs in the LUSE. This item can be filtered. You can filter by specifying an exact match in the filtering conditions.
145
External Subsystem
Description
Displays the external subsystem name. This item is displayed only for XP24000/XP20000 and XP12000/XP10000/SVS200. This item can be filtered. You can filter by specifying an exact match in the filtering conditions. 1 external-subsystem-name = Displayed when all the following conditions are satisfied: The volume is an internal volume to which an external volume is mapped. Device Manager manages the external subsystem. The external volume is allocated to the logged-in user. external-system-model#external-subsystem-serial-number = Displayed when all the following conditions are satisfied: A user assigned to the All Resources resource group is logged in. The volume is an internal volume to which an external volume is mapped. Device Manager has not managed the external subsystem. The model is such that XP External Storage Software can acquire its serial number. external-system-model = Displayed when all the following conditions are satisfied: A user assigned to the All Resources resource group is logged in. The volume is an internal volume to which an external volume is mapped. Device Manager has not managed the external subsystem. The model is such that XP External Storage Software cannot acquire its serial number. Unknown = Displayed when all of the following conditions are satisfied: The volume must be an internal volume to which an external volume is mapped. A user assigned a user-defined resource group is logged in.
No external volumes are assigned to the logged-in user. Blank = Displayed when the volume is a volume other than an internal volume to which an external volume is mapped. CMD DEV Copy Type Displays whether the LDEV is a command device (CMD DEV, Remote or blank). Displays copy type: For each P-VOL paired with multiple S-VOLs, the copy type of each pair is displayed.
None = pair status unknown This item can be filtered. You can filter by specifying a partial match in the filtering conditions. Copy Role Copy role: P-VOL, S-VOL, or Blank = ordinary volume For each P-VOL paired with multiple S-VOLs, the copy role of each pair is displayed. This item can be filtered. You can filter by specifying a partial match in the filtering conditions.
BC = XP Business Copy Software Cnt Ac-S = XP Continuous Access Synchronous Software Cnt Ac-A = XP Continuous Access Asynchronous Software Cnt Ac= XP Continuous Access Software with unidentifiable synchronous mode2 Snapshot = XP Snapshot Cnt Ac-J = XP Continuous Access Journal Software Unpaired = unpaired
146
Copy Status
Description
Copy status:
None = copy status is unknown For each P-VOL paired with multiple S-VOLs, the copy status of each pair is displayed. This item can be filtered. You can filter by specifying a partial match in the filtering conditions. Even if all the conditions are met, if the microcode of a storage subsystem that uses XP External Storage Software is not supported in the connection-destination subsystem, that external subsystem name will not be displayed. In this case, if a user assigned to the All Resources resource group is logged in, external-systemmodel#external-subsystem-serial-number is displayed. If a user assigned to a user-defined resource group is logged in, Unknown is displayed. 2 Displayed when the storage subsystem containing the XP Continuous Access Software P-VOL has not been registered in Device Manager. Since Device Manager is able to obtain information about the synchronization mode, if the target storage subsystem (S-VOL) is an XP24000/XP20000, XP12000/XP10000/SVS200 or XP1024/XP128, Cnt Ac-S or Cnt Ac-A is displayed in this column.
1
8-2-3 Viewing the Open-Reserved group for a subsystem

For the Open-Reserved group, information about the open volumes that cannot be allocated paths is displayed. The following volumes cannot be allocated paths:
THP pool volumes Data pool volumes used in XP Snapshot Journal volumes used in XP Continuous Access Journal Software Journal volumes used in Universal Replicator for Mainframe On-demand volumes Reserve volumes used in XP Auto LUN Software Volumes specified as system disks
When the Open-Reserved group for a storage subsystem is selected, the application area displays the following information:
Name: Name of the storage subsystem Number of LDEVs: Number of LDEVs/LUs for which paths cannot be allocated, for open volumes in the storage subsystem Configured Capacity*: Total capacity of LDEVs/LUs for which paths cannot be allocated, for open volumes in the storage subsystem Actual Capacity*: Total physical capacity of LDEVs/LUs for which paths cannot be allocated, for open volumes in the storage subsystem
147
All Storage/My Storage operations * The GB and TB capacity values are truncated to two decimal places, and the MB capacity values are truncated to whole numbers. Thus, the capacity shown on the Device Manager window might be less than the actual capacity available. Sortable table lists the LDEVs/LUs in the Open-Reserved group for the storage subsystem and displays detailed information for each LDEV/LU (see Table 8-3). To view the detailed information for a specific LDEV, select the desired LDEV to open the Detailed Information window. For details on the items displayed in the LDEV Detailed Information window, see Table 7-1. Table 8-3 Information for the Open-Reserved group under All Storage/My Storage Item
LDEV
Description
LDEV number. For LUSE, only a representative LDEV number is displayed. Select the link to display the Detailed Information window for the LDEV. This item can be filtered. You can filter by specifying a value range in the filtering conditions. Displays LDEV capacity. Values in GB and TB are truncated to two decimal places. Values in MB are truncated to whole numbers. So, the value shown here might be less than the actual capacity. This field also displays the size of HRX intermediate volumes. For more information on the HRX intermediate volume, see the documentation for the storage subsystem that you are using. This item can be filtered. You can filter by specifying a value range or exact match in the filtering conditions. Displays LDEV capacity information. When the volume attribute of the LDEV is THP-VOL, the physical capacity of the data storage area allocated from a THP pool is displayed. When the volume attribute of the LDEV is not THP-VOL, the same value as Capacity is displayed. When the value cannot be identified, n/a is displayed. This column is displayed only for XP24000/XP20000. This item can be filtered. You can filter by specifying a value range or exact match in the filtering conditions. Displays the LDEV type. This item is displayed for XP24000/XP20000 and XP12000/XP10000/SVS200 only.
Capacity
Consumed Capacity
Type
- = LDEV whose drive type is not identified This item can be filtered. You can filter by specifying a partial match in the filtering conditions. ArrayGroup Displays information about the array group. For XP24000/XP20000, XP12000/XP10000/SVS200, and XP1024/XP128, the value displayed is the virtual device number in the parity group. For XP512/XP48, the value displayed is the parity group number. This item can be filtered. You can filter by specifying a partial or exact match in the filtering conditions.
148
Table 8-3 Information for the Open-Reserved group under All Storage/My Storage Item
Volume Attr
Description
Displays volume attributes.
LUSE = XP LUN Expansion or LUSE volume CVS = Volume created with the XP Virtual LVI/LUN (VLL) and Volume Shredder (or
CVS) function
LUSE (CVS) = LUSE volume consisting of CVS volumes THP-VOL = THP volume THP-Pool-VOL = THP pool volume V-VOL = V-volume used in XP Snapshot POOL = Data pool volume used in XP Snapshot JNL-VOL = Journal volume used in XP Continuous Access Journal Software MF-JNL = Journal volume used in Universal Replicator for Mainframe GUARD = XP Data Retention Utility volume External = External volume IO Suppression = Volume to which an external volume is mapped, and for which the host I/O suppression mode is enabled I/O cache mode is enabled
CacheEnable = Volume to which an external volume is mapped, and for which the
OnDemand = On-demand volume Migration-reserved = Reserve volume used in XP Auto LUN Software System Disk = Volume specified as system disk
None = Ordinary volume This item can be filtered. You can filter by specifying a partial match in the filtering conditions. Pool ID When the volume attribute of the LDEV is THP-Pool-VOL, the Pool ID of the THP pool in which that LDEV is registered is displayed. When the volume attribute of the LDEV is not THP-Pool-VOL, a blank is displayed. This item is displayed only in XP24000/XP20000. This item can be filtered. You can filter by specifying an exact match in the filtering conditions. Displays the SLPR number. This item is displayed only for a storage subsystem that can use XP Disk/Cache Partition.
SLPR
0 is displayed if no SLPR is set. Inconsistent is displayed if a LUSE is used and different SLPRs are set for the
LDEVs making up the LUSE. CLPR Displays the CLPR number. This item is displayed only for a storage subsystem that can use XP Disk/Cache Partition.
0 is displayed if no CLPR is set Inconsistent is displayed if a LUSE is used and different SLPRs or CLPRs are set
for the LDEVs making up the LUSE.

EMU Type Emulation type for StorageWorks XP Disk Array. For LUSE, this item indicates the emulation type and the number of LDEVs in the LUSE. This item can be filtered. You can filter by specifying an exact match in the filtering conditions.
149
External Subsystem
Description
Displays the external subsystem name. This item is displayed only for XP24000/XP20000 and XP12000/XP10000/SVS200. This item can be filtered. You can filter by specifying an exact match in the filtering conditions. 1 external-subsystem-name = Displayed when all the following conditions are satisfied: The volume is an internal volume to which an external volume is mapped. Device Manager manages the external subsystem. The external volume is allocated to the logged-in user. external-system-model#external-subsystem-serial-number = Displayed when all the following conditions are satisfied: A user assigned to the All Resources resource group is logged in. The volume is an internal volume to which an external volume is mapped. Device Manager has not managed the external subsystem. The model is such that XP External Storage Software can acquire its serial number. external-system-model = Displayed when all the following conditions are satisfied: A user assigned to the All Resources resource group is logged in. The volume is an internal volume to which an external volume is mapped. Device Manager has not managed the external subsystem. The model is such that XP External Storage Software cannot acquire its serial number. Unknown = Displayed when all of the following conditions are satisfied: The volume must be an internal volume to which an external volume is mapped. A user assigned a user-defined resource group is logged in.
No external volumes are assigned to the logged-in user. Blank = Displayed when the volume is a volume other than an internal volume to which an external volume is mapped. CMD DEV Copy Type Displays whether the LDEV is a command device (CMD DEV, Remote, or blank). Displays copy type. For each P-VOL paired with multiple S-VOLs, the copy type of each pair is displayed.
None = pair status unknown This item can be filtered. You can filter by specifying a partial match in the filtering conditions. Copy Role Copy role: P-VOL, S-VOL, or Blank = ordinary volume For each P-VOL paired with multiple S-VOLs, the copy role of each pair is displayed. This item can be filtered. You can filter by specifying a partial match in the filtering conditions.
BC = XP Business Copy Software Cnt Ac-S = XP Continuous Access Synchronous Software Cnt Ac-A = XP Continuous Access Asynchronous Software Cnt Ac = XP Continuous Access Software with unidentifiable synchronous mode2 Snapshot = XP Snapshot Cnt Ac-J = XP Continuous Access Journal Software Unpaired = unpaired
150
Copy Status
Description
Copy status:
None = copy status is unknown. For each P-VOL paired with multiple S-VOLs, the copy status of each pair is displayed. This item can be filtered. You can filter by specifying a partial match in the filtering conditions.
1
Even if all the conditions are met, if the microcode of a storage subsystem that uses XP External Storage Software is not supported in the connection-destination subsystem, that external subsystem name will not be displayed. In this case, if a user assigned to the All Resources resource group is logged in, external-systemmodel#external-subsystem-serial-number is displayed. If a user assigned to a user-defined resource group is logged in, Unknown is displayed. 2 Displayed when the storage subsystem containing the XP Continuous Access Software with unidentifiable synchronous mode P-VOL has not been registered in Device Manager. Since Device Manager is able to obtain information about the synchronization mode, if the target storage subsystem (S-VOL) is an XP24000/XP20000, XP12000/XP10000/SVS200 or XP1024/XP128, Cnt A-S or Cnt Ac-A appears in this column.
8-2-4 Viewing the Mainframe-Unspecified group

When the Mainframe-Unspecified group for HP StorageWorks XP disk array is selected, the application area displays the following information:
Name: Name of the storage subsystem Number of LDEVs: Number of mainframe volumes in the storage subsystem Mainframe-Unspecified Capacity*: Total capacity of mainframe volumes in the storage subsystem
* The GB and TB capacity values are truncated to two decimal places, and the MB capacity values are truncated to whole numbers. Thus, the capacity shown on the Device Manager window might be less than the actual capacity available. Sortable table lists the LDEVs/LUs in the Mainframe-Unspecified group for the storage subsystem and displays detailed information for each LDEV/LU (see Table 8-4). To view the detailed information for a specific LDEV, select the desired LDEV to open the Detailed Information window For details on the items displayed in the LDEV Detailed Information window, see Table 7-1. Table 8-4 Information for the Mainframe-Unspecified group under All Storage/My Storage Item
LDEV
Description
Displays the LDEV number. For LUSE, only a representative LDEV number is displayed. Select the link to display the Detailed Information window for the LDEV. This item can be filtered. You can filter by specifying a value range in the filtering conditions.
151
Table 8-4 Information for the Mainframe-Unspecified group under All Storage/My Storage Item
VOLSER DEVN Type
Description
Displays the serial number of the LDEV volume. A blank appears if the serial number cannot be obtained. Displays all the device numbers set for the LDEV. A blank appears if the device numbers cannot be obtained. Displays the LDEV type. This column is displayed for XP24000/XP20000 and XP12000/XP10000/SVS200 only.

SLPR
#AT = The mapped external volume consists of SATA drives. #FC = The mapped external volume consists of FC drives. #SAS = The mapped external volume consists of SAS drives. #BD = The mapped external volume consists of BD drives. #- = The drive type of the mapped external volume is not identified. AT = LDEV that consists of SATA drives FC = LDEV that consists of FC drives SAS = LDEV that consists of SAS drives BD = LDEV that consists of BD drives - = LDEV whose drive type is not identified
Displays the SLPR number. This item is displayed only for a storage subsystem that can use XP Disk/Cache Partition.
0 is displayed if no SLPR is set. Inconsistent is displayed if a LUSE is used and different SLPRs are set for the LDEVs
making up the LUSE. CLPR Displays the CLPR number. This item is displayed only for a storage subsystem that can use XP Disk/Cache Partition.
0 is displayed if no CLPR is set. Inconsistent is displayed if a LUSE is used and different SLPRs or CLPRs are set for
the LDEVs making up the LUSE.

EMU Type Displays the emulation type. For LUSE, this item indicates the emulation type and the number of LDEVs in the LUSE. This item can be filtered. You can filter by specifying an exact match in the filtering conditions. Volume Attr Displays the volume attribute.
Migration-reserved = Reserve volume used in XP Auto LUN Software None = Ordinary volume
This item can be filtered. You can filter by specifying a partial match in the filtering conditions. Displays the LDEV capacity. The unit is Cyl. This item can be filtered. You can filter by specifying a partial match in the filtering conditions.
Capacity
152
Table 8-4 Information for the Mainframe-Unspecified group under All Storage/My Storage Item
External Subsyste m
Description
Displays the external subsystem name. This column is displayed only for XP24000/XP20000 and XP12000/XP10000/SVS200. This item can be filtered. You can filter by specifying an exact match in the filtering conditions. external -subsystem-name = Displayed when all the following conditions are satisfied:* The volume is an internal volume to which an external volume is mapped. Device Manager manages the external subsystem.
The external volume is allocated to the logged-in user. external -system-model#external -subsystem-serial-number = Displayed when all the following conditions are satisfied: A user assigned to the All Resources resource group is logged in. The volume is an internal volume to which an external volume is mapped. Device Manager does not manage the external subsystem. The model is such that XP External Storage Software can acquire its serial number. external -system-model = Displayed when all the following conditions are satisfied: A user assigned to the All Resources resource group is logged in. The volume is an internal volume to which an external volume is mapped. Device Manager does not manage the external subsystem. The model is such that XP External Storage Software can acquire its serial number. Unknown = Displayed when all of the following conditions are satisfied: The volume must be an internal volume to which an external volume is mapped. A user assigned to a user-defined resource group is logged in. No external volumes are assigned to the logged-in user. Blank = Displayed when the volume is a volume other than an internal volume to which an external volume is mapped.
*
Even if all the conditions are met, if the microcode of a storage subsystem that uses XP External Storage Software is not supported in the connection-destination subsystem, that external subsystem name will not be displayed. If a user assigned to the All Resources resource group is logged in, external-systemmodel#external-subsystem-serial-number is displayed. If a user assigned to a user-defined resource group is logged in, Unknown is displayed.
8-2-5 Viewing the Pools group

The Pools group displays information about the pools that can be managed by Device Manager. The Pools group is displayed only when the storage subsystem type is XP24000/XP20000. To display pool information: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 whose pool information is to be displayed, then the Pools group. The Pools subwindow appears in the application area. For the Pools group, the number of pools and their capacity are displayed for each type of pool that can be managed by Device Manager. To start managing pools, click the link to the desired pool type. Device Manager enables you to manage XP Thin Provisioning Software pools. For details about the management of XP Thin Provisioning Software pools, see section 8-8 .
153
8-3 Performing a LUN Scan operation

Users with Modify permission who are assigned the All Resources resource group can perform LUN Scan operations. When you perform a LUN Scan operation, Device Manager automatically creates logical groups for the LUNs that exist in the storage subsystem based on their connected ports and specified security. Device Manager stores LUNs that do not belong to a storage group in these logical groups. Device Manager stores the logical groups thus created within the logical group that has the same name as the storage subsystem on which the LUN Scan operation is performed under the LUN SCAN group, which is created in the Logical Groups object. As with LUNs in user-defined storage groups, you can move LUNs that are stored under the LUN SCAN group to new or existing storage groups as desired. IMPORTANT: When you perform a LUN Scan operation with XP512/XP48, LUNs that belong to the same LUN group are stored in the same logical group. NOTE: Before you perform a LUN Scan operation, we recommend that you change the name of the storage subsystem to the logical group name you wish to use. If you change the storage subsystem name after you perform the LUN Scan operation, the name of the logical group in the LUN SCAN group will no longer match the storage subsystem name. If you subsequently perform another LUN Scan operation on the same storage subsystem, another logical group is created with the same name as the updated storage subsystem name. This means that, even if the LUNs detected the first time you performed the LUN Scan operation have the same ports and security as those detected when you performed the later LUN Scan operation, they will be stored under a different logical group. Before you perform a LUN Scan operation, make sure that all of the WWNs displayed in the list of LDEVs of the target storage subsystem satisfy the following conditions:
A host with that WWN actually exists. The host with that WWN is registered as a Device Manager management target.
If you perform a LUN Scan operation without these conditions met, WWNs that are not registered as management target hosts of Device Manager are automatically registered as hosts using a temporary host name. The temporary host name is generated in the form host_consecutivenumber (example: host_1), except for WWNs that belong to XP512/XP48 WWN groups, where such names are generated in the form WWN-group-name_consecutive-number. If such a temporary host name is registered, you must change it to match that of the actual host, or you must consolidate the WWNs so that they match the physical configuration of the hosts. If you install Device Manager agent on the host, host name changing and consolidation of the WWNs is performed automatically, but the temporary hosts registered by the LUN Scan operation may remain as unused information. In this case, delete the temporary hosts that are no longer required. NOTE: If you display the contents of the LUN SCAN group while LUN Scan is being executed and before the operation is completed, the value displayed for the number of LUNs may be less than the actual number. To display the correct LUN count, display the contents of the LUN SCAN group again after LUN Scan ends. To perform a LUN Scan operation: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage/My Storage object tree in the navigation area to display the groups for each storage subsystem available to the logged-in user. Select the Open-Allocated group of the storage subsystem for which you want to perform a LUN Scan. A LUN Scan can be performed from the Subsystems object. In the Explorer menu, select Resources and then Subsystems and then in the navigation area, select and expand the Subsystems object. Then, select the storage subsystem for which the LUN Scan is to be performed.
154
All Storage/My Storage operations 3. In the application bar area, click the LUN Scan button. The LUN Scan-Confirmation window appears. 4. To execute the LUN scan, click the OK button. To cancel the LUN scan execution request, click the Cancel button. Device Manager scans the selected storage subsystem for any LUNs not allocated to a storage group and places those LUNs in the LUN SCAN group. It also updates LUN information for the Open-Allocated group using the information that was detected by the LUN Scan. For LUN information displayed in the Open-Allocated group, see section 8-2-1 .
8-4 Allocating storage

Users with Modify permission can allocate a path to storage. When you allocate storage, you allocate one or more access paths (specifying ports and LUNs) to LDEV(s). You can optionally secure the new LUN(s) to host WWN(s) and/or allocate LDEVs that are unallocated or already allocated. You can also allocate a volume path when you add storage to a storage group (see section 7-6-2 ). To allocate storage: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage /My Storage object tree in the navigation area, and then select the storage subsystem and group (Open-Allocated or Open-Unallocated) that contains the LDEV(s) that you want to allocate. 3. Select the LDEV(s) to which you want to allocate a volume path, and then click the Allocate Storage button. The Add Storage (STEP: Define Host/Port Connections) dialog box appears. In one operation, you can select a maximum of 100 LDEVs. If you want to perform an operation on more than 100 LDEVs, perform the operation multiple times, selecting no more than 100 LDEVs in each operation. 4. For the storage allocations procedures you can perform in this dialog box and subsequent tasks, see step 6 onward in section 7-6-2 .
8-5 Unallocating storage

Users with Modify permission can unallocate storage. When you unallocate storage, you remove one or more access paths from an LDEV. When you unallocate a LUSE volume, you can also optionally delete the LUSE volume to make its individual LDEVs available for use. Before deleting a path or LUN, take the following precautions:
Before deleting a path, make sure that the path is no longer in use. Before deleting a LUN, make sure that no access is underway from a host. When a LUN is deleted, all I/Os that are being executed between a host and that LUN are canceled.
CAUTION: For command device and copy pair volumes: For XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, you cannot unallocate the last volume path from a logical device that is specified as a copy pair volume. For the XP512/XP48, you cannot unallocate the last volume path from a logical device that is specified as a command device or as a copy pair volume.
To unallocate storage: 1. In the Explorer menu, select Resources and then All Storage or My Storage.
155
All Storage/My Storage operations 2. Expand the All Storage/My Storage object tree in the navigation area, select the storage subsystem that contains the LDEV(s) that you want to unallocate and then select the OpenAllocated group. 3. Select the desired LDEV(s) and click the Unallocate Storage button. In one operation, you can select a maximum of 100 LDEVs. If you want to perform an operation on more than 100 LDEVs, perform the operation multiple times, selecting no more than 100 LDEVs in each operation. 4. If you selected a volume with more than one path, Device Manager displays the paths and asks you to select the path(s) to be deleted (see Figure 8-1). Select the desired path(s), and click the OK button to continue, or click the Cancel button to cancel your request to unallocate storage.
Figure 8-1 Selecting the path(s) window 5. When the confirmation panel appears (see Figure 8-2), read and observe the warning. Click the OK button to go ahead and delete the specified path(s), or click the Cancel button to cancel your request to unallocate storage.
156
Figure 8-2 Unallocating storageconfirmation window 6. If all paths of a LUSE volume are being deleted, Device Manager displays a confirmation message asking if you want to keep or delete the LUSE volume (see Figure 8-3). For the XP512/XP48, LUSE is always deleted.
Figure 8-3 Unallocating storage LUSEconfirmation window 7. Consider carefully the Warning message in the LUSE confirmation window. CAUTION: The delete LUSE operation is destructive. Read and observe the important warning on the LUSE Confirmation window.
If it is acceptable to lose the data on the LUSE volume, to delete a LUSE volume by
clicking, the YES, I have confirmed it check box, and then clicking the Delete LUSE.
To retain the LUSE volume, click the Keep LUSE button.
157
All Storage/My Storage operations Exception: For XP512/XP48, you cannot cancel the LUSE deletion for the XP512/XP48. The LUSE is deleted when the path is deleted. A message notifies you when the unallocate storage operation is complete. When a path allocated to an LDEV or LU is released, the LDEV or LU is moved to the Open-Unallocated group of the storage subsystem.
8-6 Creating LUSE volumes

Device Manager enables you to use the following methods to create a LUSE volume:
You can create a LUSE volume when you allocate paths to LDEVs (see section 7-6-2 ). You can create a LUSE volume using an LDEV with an allocated path as the representative LDEV (see section 8-6-2 ). This method is applicable to XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128. You can create a LUSE volume by combining LDEVs with no allocated path (see section 8-6-3 ). This method is applicable to XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128.
8-6-1 Requirements of LDEVs that constitute a LUSE volume

There are requirements for the LDEVs that constitute a LUSE volume in each storage subsystem. Table 8-5 shows the requirements of LDEVs that make up a LUSE volume. Table 8-5 Requirements of LDEVs that make up a LUSE volume Requirements XP24000/ XP20000 XP12000/ XP1024/XP128 XP10000/SVS200
Yes Yes Yes Yes
XP512/XP48
Yes Yes
No path must be allocated. Yes

1
Must not be a command device or a remote command device. Must not make up a copy pair. 2 Must not be registered as an external volume. Must not be a LUSE. Must be the same 3 emulation type. Must have the same RAID level. Must not be a reserved volume for XP Auto LUN Software. The internal volumes must not coexist with internal volumes to which external volumes are mapped.
Yes
Yes Yes Yes Yes Yes
Yes Yes Yes Yes Yes
Yes Yes Yes Yes Yes
Yes Yes Yes Yes Yes Yes
Yes
Yes
158
Table 8-5 Requirements of LDEVs that make up a LUSE volume Requirements XP24000/ XP20000 XP12000/ XP1024/XP128 XP10000/SVS200
Yes -
XP512/XP48
-
The internal volumes to Yes which external volumes are mapped must have the same host I/O suppression mode. The internal volumes to Yes which external volumes are mapped must have the same I/O cache mode. Must not be a THP volume. Yes Must be located in the same control unit. The CVS volumes must not coexist with normal volumes. All the LDEVs must be the same size. An LDEV set to the GUARD mode cannot be used. 4 Yes -
Yes
Yes Yes
Yes Yes
Yes
Yes -
Yes -
The host mode of a port or Yes host storage domain whose path is allocated to an LDEV cannot be 0x0C. 4 The host mode of a port or Yes host storage domain whose path is allocated to an 4 LDEV cannot be 0x01. Each LDEV must belong to a storage subsystem whose microcode is 21-0505-00/00 or later. 4
1
Yes
Yes
This requirement does not apply to the representative LDEV when a LUSE volume is created with pathallocated LDEVs in XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128. 2 If you create a LUSE volume by using LDEVs for which paths have not been allocated, an XP Snapshot VVOL can be used to create a LUSE with another XP Snapshot V-VOL. 3 You can only use the LDEVs of the following emulation types: OPEN-3, OPEN-8, OPEN-9, OPEN-K, OPEN-E, OPEN-L, OPEN-M, and OPEN-V 4 This requirement is applicable when a LUSE volume is created with path-allocated LDEVs.
8-6-2 Creating a LUSE volume with LDEVs with allocated paths

In XP24000/XP20000, XP12000/XP10000/SVS200, and XP1024/XP128, you can create a LUSE volume using a path-allocated LDEV as the representative LDEV. To do this, start from the OpenAllocated subwindow.
159
NOTE: An LDEV with allocated paths can only be used as a representative LDEV. WARNING: If you create a LUSE volume by using LDEVs for which paths have been allocated, data stored in LDEVs without such paths will be lost. The user is responsible for backing up the data before creating a LUSE volume. NOTE: When you create a LUSE volume by using LDEVs for which paths have been allocated, the LDEVs to be used have the following conditions. The appropriate OS must be running on the host assigned to the target LDEVs The appropriate host mode must be used for the host storage domain whose path is assigned to the
target LDEVs
For details on the OS requirements and which host mode to specify for each host OS, see the XP LUN Expansion manual for each storage subsystem. To create a LUSE volume with LDEVs with allocated paths: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, select the storage subsystem for which you want to create a LUSE volume, and then select the Open-Allocated group. The Open-Allocated subwindow appears in the application area. 3. In the Open-Allocated subwindow, select one LDEV that is to be the representative LDEV for the LUSE volume to be created, and then click the Create LUSE button. The Create LUSE-subsystem-name dialog box appears. This dialog box displays a list of LDEVs that can be combined with the LDEVs selected in the Open-Allocated subwindow to create the LUSE volume. If there are no LDEVs that can be used to create the LUSE volume, No Object is displayed. In such a case, return to the Open-Allocated subwindow and select another representative LDEV. 4. In the Create LUSE-subsystem-name dialog box, select the LDEVs to be used to create the LUSE volume, and then click the OK button. The Create LUSE-Confirmation dialog box appears. 5. Check the LDEVs to be used. To create the LUSE volume, select the Yes. I have confirmed it. check box, and then click the Confirm button. To cancel creation of the LUSE volume, click the Cancel button. If your attempt to create the LUSE volume fails, an error message is displayed. You can reexecute the operation by clicking the Back button to return to the Create LUSE - Confirmation dialog box.
8-6-3 Creating a LUSE volume with LDEVs with no allocated path

CAUTION:If you create a LUSE volume by using LDEVs for which paths have not been allocated, data stored in the LDEVs will be lost. The user is responsible for backing up the data before creating a LUSE volume. In XP24000/XP20000, XP12000/XP10000/SVS200, and XP1024/XP128, you can create a LUSE volume by combining LDEVs with no allocated path. To do this, start from the Open-Unallocated subwindow. To create a LUSE volume with LDEVs with no allocated path: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, select the storage subsystem for which you want to create a LUSE volume, and then select the OpenUnallocated group.
160
All Storage/My Storage operations The Open-Unallocated subwindow appears in the application area. 3. In the Open-Unallocated subwindow, select the LDEVs that are to be used to create the LUSE volume, and then click the Create LUSE button. The Create LUSE-subsystem-name dialog box appears. You can select a maximum of 128 LDEVs in one operation. If you want to include more than 128 LDEVs, select them in multiple operations, selecting no more than 128 LDEVs in each operation. 4. In the Create LUSE-subsystem-name dialog box, select the LDEVs that are to be used to create the LUSE volume, and then click the Create LUSE button (see Figure 8-4).
Figure 8-4 Creating LUSEselecting LDEVs The LUSE volume to be created using the selected LDEVs is displayed in LUSE LUs. Repeat this step as many times as there are LUSE volumes to be created. To release a defined LUSE volume and then re-create it, select the LUSE volume from LUSE LUs and then click the Cancel LUSE button. NOTE: You cannot delete/reconstruct existing LUSE volumes during this procedure. You must delete a LUSE volume first in order to use the individual LDEVs. NOTE: For a storage subsystem that is using XP Disk/Cache Partition, do not create a LUSE volume by using LDEVs with different SLPRs and CLPRs. If the SLPRs differ, the partitioned storage administrator cannot manage the storage subsystem. If the CLPRs differ, the effectiveness of the cache partitioning may decrease. 5. For XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, the smallest LDEV number in the LUSE volume automatically becomes the representative LDEV number of a new LUSE volume. 6. Check the settings in the Create LUSE-subsystem-name dialog box, and then click the OK button. To cancel creation of the LUSE volume, click the Cancel button. The Create LUSE-Confirmation dialog box appears. Check the displayed information and read the warning. 7. If it is acceptable to lose data on the LDEVs that will constitute the LUSE volume, select the Yes. I have confirmed it. check box, and then click the Confirm button. Click the Cancel button to cancel your request.
161
All Storage/My Storage operations If your attempt to create LUSE volumes fails, an error message is displayed. You can reexecute the operation by clicking the Back button to return to the Create LUSE-Confirmation dialog box.
8-7 Deleting LUSE volumes

CAUTION: Be sure to back up data before deleting a LUSE volume. When you delete a LUSE volume, the data stored on it will be lost. Users with the Modify permission can delete a LUSE volume with no allocated path and split it into its individual LDEVs. For the XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128 storage subsystems, users with Modify permission can also delete LUSE volumes by unallocating storage (see section 85 ). NOTE: This operation cannot be performed on the XP512/XP48. An XP512/XP48 LUSE volume is automatically deleted when the last access path is removed (see section 8-5 ). To delete LUSE volumes with no allocated path: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage/My Storage object tree in the navigation area, select the storage subsystem for which you want to delete LUSE volumes and then select the Open-Unallocated group. The Open-Unallocated subwindow appears in the application area. 3. Select the desired LUSE volumes and then click the Delete LUSE button. The Delete LUSE-Confirm dialog box appears. You can select a maximum of 100 LUSE volumes in one operation. If you want to delete more than 100 LUSE volumes, select them in multiple operations, selecting no more than 100 LUSE volumes in each operation. 4. In the Delete LUSE-Confirm dialog box, check the displayed information and read the warning. If it is acceptable to lose data on the LUSE volumes, select the Yes. I have confirmed it. check box and then click the Confirm button to delete the LUSE volumes. 5. To cancel your request to delete the LUSE volumes, click the Cancel button.
8-8 Managing XP Thin Provisioning Software pools

Users with the Modify permission can manage XP Thin Provisioning Software pools. Users with the View permission can only view information about XP Thin Provisioning Software pools. XP Thin Provisioning Software pool operations include the following:
Viewing XP Thin Provisioning Software pools (see section 8-8-1 ) Managing THP pools (see section 8-8-2 ) Managing THP volumes (see section 8-8-3 ) Viewing information about THP volumes that are not assigned to THP pools (see section 8-8-4 )
162
8-8-1 Viewing XP Thin Provisioning Software pools

Users with the View permission can view the properties of XP Thin Provisioning Software, information about the THP pools in XP Thin Provisioning Software, information about the THP pool volumes registered in THP pools, and information about the THP volumes assigned to THP pools. To view XP Thin Provisioning Software pools: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 to be manipulated, the Pools group, and then Thin Provisioning. The Thin Provisioning subwindow is displayed in the application area. The sortable table in the Thin Provisioning subwindow displays a list of THP pools that have been created in the selected storage subsystem. From the Thin Provisioning subwindow, you can start the following THP pool management operations:
Viewing THP pools

For information on performing operations on the THP pools displayed in the sortable table, go to step 3.
Viewing THP volumes that are not assigned to THP pools

If there are THP volumes that are not assigned to THP pools, Unassigned is displayed in the sortable table for the group. For details about the Unassigned group, see section 8-8-4 .
Creating THP pools (see section 8-8-2-1 ) Deleting THP pools (see section 8-8-2-4 )
3. In the sortable table in the Thin Provisioning subwindow, click the pool ID link of the THP pool that you want to view. The THP pool-ID subwindow appears in the application area. From the application bar area of the THP pool-ID subwindow, you can perform the following THP pool management operations (see section 8-8-2 ):
Expanding the capacity of a THP pool (see section 8-8-2-3 ) Deleting a THP pool (see section 8-8-2-4 ) Changing a THP pool's threshold value (see section 8-8-2-2 )
4. In the THP pool-ID subwindow, click the THP Pool VOL tab. A list of the THP pool volumes that have been registered in the THP pool is displayed. If you want to view the detailed information for a specific LDEV, select the desired LDEV to open the Detailed Information-LDEV-number dialog box. For details on the items displayed in this dialog box, see section 7-6-1 . 5. In the THP pool-ID subwindow, click the THP VOL tab. A list of the THP volumes assigned to the THP pool is displayed. From the THP VOL tab, you can start the following THP volume management operations:
Creating THP volumes (see section 8-8-3-1 ) Deleting THP volumes (see section 8-8-3-3 ) Changing a THP volume threshold value (see section 8-8-3-2 )
If you want to view the detailed information for a specific LDEV, select the desired LDEV to open the Detailed Information-LDEV-number dialog box. For details on the items displayed in this dialog box, see section 7-6-1 .
8-8-2 Managing THP pools

Users with the Modify permission can create THP pools, change threshold values, expand capacity, and delete THP pools. The following THP pool operations are supported: 163
Creating a THP pool (see section 8-8-2-1 ) Changing the THP pool threshold value (see section 8-8-2-2 ) Expanding the capacity of a THP pool (see section 8-8-2-3 ) Deleting THP pools (see section 8-8-2-4 )
8-8-2-1 Creating a THP pool

Users with the Modify permission can create a THP pool by registering THP pool volumes. The following are the requirements for LDEVs that can be used as THP pool volumes:
The capacity must be in the range from 8 GB to 4 TB. The LDEV must not be a LUSE volume. The LDEV must not be a pair volume for XP Business Copy Software, XP Continuous Access Software, XP Continuous Access Journal Software, or XP Snapshot. The LDEV must not be a reserved volume for XP Auto LUN Software. The LDEV must not be a pool volume or journal volume. The status of the LDEV must be Normal. The volume attribute must not be Guard. The emulation type must be OPEN-V. The LDEV must not be a volume for XP Snapshot V-VOL or XP Thin Provisioning Software THP. The LDEV must not be a command device. No paths can have been allocated. If you register multiple LDEVs, they must have the same CLPR number. If you register multiple LDEVs, they must have the same cache mode. If you register multiple LDEVs, they can be either internal volumes or internal volumes to which external volumes are mapped, but you cannot specify both types. If you use internal volumes to make up a THP pool, their logical units must have the same type of LDEVs. The LDEV must not be a system disk.
To create a THP pool: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 to be manipulated, the Pools group, and then Thin Provisioning. The Thin Provisioning subwindow is displayed in the application area. 3. Click the Create THP Pool button. The Create THP Pool (Step 1: Introduction) dialog box appears. 4. Check the THP pool creation procedure, and then click the Next button. The Create THP Pool (Step 2: Create THP Pool) dialog box (see Figure 8-5) appears.
164
Figure 8-5 Create THP Pool (Step 2: Create THP Pool) dialog box 5. Select a pool ID for the new THP pool to be created. Pool IDs 0 through 127 are displayed. The radio buttons for the pool IDs that have already been assigned are disabled, and for each such pool ID the name of the software product that uses that pool ID is displayed in the Type column. The default is that the smallest pool ID that has not been assigned to any THP pool is selected. You can create a maximum of 128 THP pools. If there are already 128 THP pools, an error message is displayed, in which case you must delete an unneeded THP pool, and then perform the operation again (see section 8-8-2-4 ). 6. Select a THP pool usage threshold value from the drop-down list. The threshold value must be a multiple of 5 in the range 5 to 95. At first, the default value, 70, is selected. 7. Check the specified information in the Create THP Pool (Step 2: Create THP Pool) dialog box. If the information is correct, click the Next button to proceed to the next step. The Create THP Pool (Step 3: Select THP Pool VOL(s)) dialog box (see Figure 8-6) appears.
165
Figure 8-6 Create THP Pool (Step 3: Select THP Pool VOLs) dialog box If there are no THP pool volumes that can be registered into the THP pool, an error message is displayed and No Object is displayed in the Selectable LDEVs sortable table. 8. Select the THP pool volumes that are to be registered in the THP pool, and then click the Next button to proceed to the next step. The Create THP Pool (Step 4: Confirm) dialog box appears. 9. In the Create THP Pool (Step 4: Confirm) dialog box, select the configuration check box to create the THP pool based on the specified information, and then click the Confirm button. To return to the Create THP Pool (Step 3: Select THP Pool VOL(s)) dialog box, click the Back button. To cancel THP pool creation, click the Cancel button. Clicking the Confirm button displays the Create THP Pool (Step 5: Finish) dialog box. 10. Click the Finish button to close the dialog box. If an error occurs during creation of a THP pool, click the Back button to return to the previous step and correct the settings.
8-8-2-2 Changing the THP pool threshold value

Users with the Modify permission can change the threshold value for the THP pool usage rate. NOTE: This operation can be performed only for THP pools whose status is Normal. To change the threshold value for the THP pool usage rate: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 to be manipulated, the Pools group, and then Thin Provisioning. The Thin Provisioning subwindow is displayed in the application area. 3. Click the Pool ID link of the THP pool whose threshold value you want to change. The THP pool-ID subwindow appears in the application area. 4. Click the Modify THP Pool button. The Modify THP Pool dialog box appears (see Figure 8-7).
166
Figure 8-7 Modify THP Pool dialog box 5. Select the new threshold value from the drop-down list. The threshold value must be a multiple of 5 in the range 5 to 95. 6. Check the information specified in the Modify THP Pool dialog box. If the specified information is correct, click the OK button. To cancel the change to the threshold value, click the Cancel button.
8-8-2-3 Expanding the capacity of a THP pool

Users with the Modify permission can expand the capacity of a THP pool by registering additional THP pool volumes into the THP pool. For the requirements for LDEVs that can be used as THP pool volumes, see section 8-8-2-1 . To expand the capacity of a THP pool: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 to be manipulated, the Pools group, and then Thin Provisioning. The Thin Provisioning subwindow is displayed in the application area. 3. Click the Pool ID link of the THP pool that you want to expand. The THP pool-ID subwindow appears in the application area. 4. Click the Expand THP Pool button. The Expand THP Pool (Step 1: Setting Information) dialog box appears. 5. Select the THP pool volumes that are to be registered into the THP pool and then click the OK button. The Expand THP Pool (Step 2: Confirm) dialog box appears. If there are no THP pool volumes that can be registered into the THP pool, an error message is displayed and No Object is displayed in the Available LDEVs sortable table. 6. Check the capacity of the THP pool before and after expansion and the information about the LDEVs that will be used as THP pool volumes. If the information is correct, click the OK button. To return to the Expand THP Pool (Step 1: Setting Information) dialog box, click the Back button. To cancel expansion of the THP pool's capacity, click the Cancel button. For the capacity of the expanded THP pool, the capacity of the THP pool before expansion plus the capacities of the new THP pool volumes that are to be added is displayed. However, 167
All Storage/My Storage operations note that the value displayed in the dialog box may not match the exact actual capacity of the THP pool because some space is used for managing the THP pool.
8-8-2-4 Deleting THP pools

Users with the Modify permission can delete THP pools. NOTE: Before deleting a THP pool, you must delete all of the THP volumes assigned to that THP pool. For details on how to delete THP volumes, see section 8-8-3-3 . To delete THP pools: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 to be manipulated, the Pools group, and then Thin Provisioning. The Thin Provisioning subwindow is displayed in the application area. IMPORTANT: You can also delete a THP pool by clicking the Delete THP Pool button in that THP pool's THP pool-ID subwindow. However, this method enables you to delete only the one THP pool that is displayed in the window. To delete multiple THP pools, you must select the THP pools to be deleted from the Thin Provisioning subwindow, and then execute the deletion process explained here. 3. In the sortable table in the Thin Provisioning subwindow, select the THP pools to be deleted, and then click the Delete THP Pools button. The Delete THP Pools dialog box appears. You can select a maximum of 10 THP pools at one time. 4. Click the information about the THP pools to be deleted. If the information is correct, click the OK button. To cancel deletion of the selected THP pools, click the Cancel button.
8-8-3 Managing THP volumes

Users with the Modify permission can create THP volumes, change threshold values, and delete THP volumes. The following THP volume operations are supported:
Creating THP volumes (see section 8-8-3-1 ) Changing a THP volume's usage rate threshold value (see section 8-8-3-2 ) Deleting THP volumes (see section 8-8-3-3 )
8-8-3-1 Creating THP volumes

Users with the Modify permission can create THP volumes. THP pools to be assigned to THP volumes, THP volume capacity, usage rate threshold value, number of THP volumes to be created, and emulation type can be specified. To create new THP volumes: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 to be manipulated, the Pools group, and then Thin Provisioning. The Thin Provisioning subwindow is displayed in the application area. 3. Click the Pool ID link of the THP pool to be assigned to THP volumes. The THP pool-ID subwindow appears in the application area. 4. Click the THP VOL tab. A list of the THP volumes assigned to the THP pool is displayed.
168
All Storage/My Storage operations 5. Click the Create THP VOLs button. The Create THP VOLs (Step 1: Introduction) dialog box appears. 6. Check the THP volume creation procedure and then click the Next button. The Create THP VOLs (Step 2: Create THP VOLs) dialog box appears (see Figure 8-8).
Figure 8-8 Create THP VOLs (Step 2: Create THP VOLs) dialog box 7. Set the volume capacity, usage rate threshold value, number of volumes to be created, and emulation type of the new THP volumes to be created. The threshold value must be a multiple of 5 in the range 5 to 300. At first, the default value, 5, is selected. You can create a maximum of 10 THP volumes at one time. To create more than 10 THP volumes, perform the process again. The only emulation type that can be set for THP volumes is OPEN-V. If you are creating multiple THP volumes, the values specified in the Create THP VOLs (Step 2: Create THP VOLs) dialog box are set for all THP volumes being created. 8. Check the specified information in the dialog box. If the information is correct, click the Next button. The Create THP VOLs (Step 3: Edit THP VOLs) dialog box (see Figure 8-9) appears.
169
Figure 8-9 Create THP VOLs (Step 3: Edit THP VOLs) dialog box 9. Check the properties of the new THP volumes that are to be created. To change property information, click the Auto link for the applicable THP volumes in order to proceed to step 10. To create the THP volumes using the displayed properties, click the Next button to proceed to step 12. If you set the LDEV number to Auto and then create THP volumes, the Device Manager server automatically assigns LDEV numbers to the THP volumes. Clicking the Auto link displays the Edit THP VOL dialog box (see Figure 8-10).
Figure 8-10 Edit THP VOL dialog box Clicking the Next button displays the Create THP VOLs (Step 4: Confirm) dialog box. 10. Change the LDEV numbers, capacity, usage rate threshold value, and emulation type of the selected THP volumes.
170
All Storage/My Storage operations Specify an LDEV number in the format LDKC-number:CU-number:LDEV-number. To have LDEV numbers assigned automatically to the THP volumes without specifying individual LDEV numbers, specify Auto. The specifiable capacity must be in the range 47 to 3,145,663 MB. At first, the default value, 47 MB, is set. A threshold value must be a multiple of 5 in the range 5 to 300. The only emulation type that can be set for THP volumes is OPEN-V. 11. Check the information specified in the Edit THP VOL dialog box. If the information is correct, click the OK button to return to the Create THP VOLs (Step 3: Edit THP VOLs) dialog box. To cancel editing of THP volume properties, click the Cancel button. In the Create THP VOLs (Step 3: Edit THP VOLs) dialog box, clicking the Next button displays the Create THP VOLs (Step 4: Confirm) dialog box. 12. To create the THP volumes based on the information specified in the Create THP VOLs (Step 4: Confirm) dialog box, select the configuration check box and then click the Confirm button. To return to the Create THP VOLs (Step 3: Edit THP VOL(s)) dialog box, click the Back button. To cancel THP volume creation, click the Cancel button. Clicking the Confirm button displays the Create THP VOLs (Step 5: Finish) dialog box. 13. Click the Finish button to close the dialog box. If an error occurs during creation of THP volumes, click the Back button to return to the previous step and correct the settings.
8-8-3-2 Changing a THP volume threshold value

Users with the Modify permission can change the threshold value for a THP volume's usage rate. To change the threshold value for a THP volume's usage rate: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 to be manipulated, the Pools group, and then Thin Provisioning. The Thin Provisioning subwindow is displayed in the application area. 3. Click the Pool ID link of the THP pool assigned to the THP volume whose threshold value is to be changed. The THP pool-ID subwindow appears in the application area. 4. Click the THP VOL tab. A list of THP volumes assigned to the THP pool is displayed. 5. In the sortable table on the THP VOL tab, select the THP volume whose threshold value is to be changed, and then click the Modify THP VOL button. The Modify THP VOL dialog box (see Figure 8-11) appears.
171
Figure 8-11 Modify THP VOL dialog box 6. Change the threshold value for the THP volume's usage rate. The threshold value must be a multiple of 5 in the range 5 to 300. 7. Check the specified information in the Modify THP VOL dialog box. If the specified information is correct, click the OK button. To cancel the threshold value change, click the Cancel button.
8-8-3-3 Deleting THP volumes

Users with the Modify permission can delete any desired THP volumes. If THP volumes are deleted, THP volumes belonging to the same array group are also deleted. Before deleting THP volumes, make sure that the following conditions are satisfied in the THP volumes to be deleted:
No paths have been allocated. The volume attribute must not be GUARD.
CAUTION: If a THP volume is deleted, data stored in the THP volume will be lost. Make sure that a THP volume to be deleted is no longer in use. To delete any desired THP volume: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 to be manipulated, the Pools group, and then Thin Provisioning. The Thin Provisioning subwindow is displayed in the application area. 3. Click the Pool ID link of the THP pool that you want to view. The THP pool-ID subwindow appears in the application area. 4. Click the THP VOL tab. A list of THP volumes assigned to the selected THP pool is displayed. 5. In the sortable table on the THP VOL tab, select the THP volumes to be deleted, and then click the Delete THP VOLs button. The Delete THP VOLs dialog box appears.
172
All Storage/My Storage operations You can delete a maximum of 10 THP volumes with one operation. If you want to delete more than 10 THP volumes, perform this operation repeatedly, selecting no more than 10 volumes each time. 6. Check the information about the THP volumes to be deleted, and then click the OK button. Other THP volumes belonging to the same array group will also be deleted. If deleting both the THP volumes to be deleted and other THP volumes belonging to the same array group is not a problem, select the check box for confirmation, and then click the OK button. To cancel deletion of the THP volumes, click the Cancel button.
8-8-4 Viewing information about THP volumes not assigned to THP pools
Users with the View permission can view information about THP volumes that are not assigned to THP pools. You can display the number of such volumes, their capacity, and a listing of the volumes. To view information about THP volumes that are not assigned to THP pools: 1. In the Explorer menu, select Resources and then All Storage or My Storage. 2. Expand the All Storage (My Storage) object tree in the navigation area, and select the XP24000/XP20000 to be manipulated, the Pools group, and then Thin Provisioning. The Thin Provisioning subwindow is displayed in the application area. 3. Click the Unassigned link. The Unassigned subwindow appears in the application area. The sortable table displays a list of THP volumes that are not assigned to THP pools. If you want to view the detailed information for a specific LDEV, select the desired LDEV to open the Detailed InformationLDEV-number dialog box. For details on the items displayed in this dialog box, see section 7-61.
173

This chapter describes Device Manager host operations:
Overview of Device Manager host operations (see section 9-1 ) Information that can be acquired from the Device Manager agent (see section 9-2 ) Viewing the list of hosts (see section 9-3 ) Adding a host (see section 9-4 ) Viewing host properties and volume information (see section 9-5 ) Modifying host properties (see section 9-6 ) Adding storage from host management (see section 9-7 ) Updating (refreshing) host information (see section 9-8 ) Managing copy pairs (see section 9-9 ) Removing a host (see section 9-10 ) Applying WWN information when replacing host bus adapters (see section 9-11 )
9-1 Overview of Device Manager host operations

A computer system that uses storage on a subsystem is referred to as a host. The Device Manager agents installed on these hosts periodically send information about the hosts and the storage used by the hosts to the Device Manager server. This enables monitoring of how the hosts use the storage in the storage subsystems managed by Device Manager. Device Manager can handle a collection of one or more World Wide Names (WWN) or iSCSI names that can be manipulated as a group as if they were a host. If you have not installed the Device Manager agent on a host, you can set a Device Manager host on the basis of the configuration of the physical host. Also, you can set a Device Manager host on the basis of a group of WWNs or iSCSI names that access a specific storage in a storage subsystem managed by Device Manager. For external volumes that are managed by the external storage subsystem, the external port used in XP External Storage Software operates in the same manner as a host. Therefore, Device Manager manages the external port as a host. From the Explorer menu, choosing Resources and then Hosts to display the Hosts object tree in the navigation area. Select Hosts in the navigation area to access host operations (see Figure 9-1).
174
Figure 9-1 Hosts object
9-2 Information that can be acquired from the Device Manager agent
When a Device Manager agent is installed on a host, the web client acquires the WWN information of the host and the LDEV information related to the host, from the Device Manager agent running on that host. The following information is acquired from the Device Manager agent:
Information displayed at World Wide Names/iSCSI Names in the host-name subwindow Host name
Note: For a host on which a Device Manager agent is not installed, the WWNs and host name that were specified when Device Manager was added to the host are displayed. For details on how to add a host, see section 9-4 . The following LDEV attributes are sent from the Device Manager agent running on a host:
File System % Used Copy Type Copy Role Copy Status Last Updated
NOTE: Information of copy type, copy role, or copy status can also be acquired from a storage subsystem.
Information that can be acquired from the Device Manager agent differs, depending on the host configuration. The following sections describe the information displayed in the web client for each host configuration.
When a host has a single path configuration (see section 9-2-1 ) 175
When a host has a multi-path configuration (see section 9-2-2 ) When a host has no path assigned (see section 9-2-3 )
9-2-1 When a host has a single path configuration

When a host has a single path configuration, the web client displays the information about LDEVs assigned to the host. The information about all of the WWNs, host names, and LDEVs loaded on the host is sent from the Device Manager agent for display by the web client.
9-2-2 When a host has a multi-path configuration

When a host has a multi-path configuration, the following information is displayed in the World Wide Names field of the host-name subwindow and for the LDEV information. The information to be displayed differs depending on the host OS, whether HBA API libraries are installed, and whether path management software is installed. Table 9-1 Information displayed in a multi-path configuration Host configuration OS Path management software1
Installed
Displayed information HBA API World Wide Names LDEV information2
Windows Solaris
Installed Not installed
All WWNs registered Only for active paths in the host Only WWNs assigned to active paths Only for active paths
Not installed Linux AIX HP-UX --
---
All WWNs registered For all paths in the host All WWNs registered For all paths in the host
Legend: -- = Whether it is installed does not affect the display. : The information to be displayed differs, depending on whether the following path management software is installed: Windows MPIO (in Windows), or HDLM for Sun Solaris or Sun StorEdge Traffic Manager (in Solaris). 2 : The LDEV information (% Used, File System, Copy Type, Copy Role, Copy Status, and Last Updated) to be acquired from the Device Manager agent.
1
For details on the required HBA API libraries for each host OS, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
9-2-3 When a host has no path assigned

When a host has no path assigned, the information displayed in World Wide Names in the hostname subwindow differs depending on the host OS and whether the HBA API libraries are installed.
176
Table 9-2 Information displayed when a host has no path assigned Host configuration OS
Windows Solaris Linux AIX HP-UX
Displayed information HBA API

Installed Not installed --
World Wide Names

All WWNs registered in the host WWNs are not displayed. All WWNs registered in the host.
Legend: -- = Whether it is installed does not affect the display.
For details on the required HBA API libraries for each host OS, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
9-3 Viewing the list of hosts

All Device Manager users can view the list of hosts for which they have access permission. To view the list of hosts in the application area, in the Explorer menu select Resources and then Hosts (see Figure 9-1). The list of hosts the application area displays the name, IP address, storage capacity, and host type for each host. The following buttons are displayed in the application area:
Add Host button Adds a host to Device Manager. Remove Hosts button Deletes the selected hosts.
When a user for whom All Resources is assigned as a resource group logs in, the External Array Nodes object appears next to the regular hosts under the Hosts object in the navigation area. The external port is displayed under the External Array Nodes object. Device Manager handles the external port as a host. When you select the External Array Nodes object in the navigation area, host attributes are displayed in the application area in the same manner as when the Hosts object is selected. However, because you cannot add or delete an external port, the Add Host button and Remove Host button are not displayed; the IP address is not displayed either. When you select a host that you want to view in the navigation area or application area, the application bar area displays operation buttons that can be executed for the selected host. The application area displays information about the host (see section 9-5 ).
9-4 Adding a host

In the web client, hosts can be added by the following methods:
Adding hosts by using the Device Manager agent (see section 9-4-1 ) Adding hosts manually (see section 9-4-2 )
177
9-4-1 Adding hosts by using the Device Manager agent

If the Device Manager agent is installed on a host and the HiScan command is executed on that host, the Device Manager agent sends detailed information about the host to the Device Manager server, and the Device Manager server adds the new host according to the information received from the Device Manager agent. If the WWN or iSCSI name of the host to be added is the same as the WWN or iSCSI name of the host that is already added to Device Manager, Device Manager moves the WWN or iSCSI name from the existing host to the host to be added. Once the WWN or iSCSI name has moved, the existing host becomes empty and must be removed. Delete the existing host, and then refresh the storage subsystem. For details on the Device Manager agent, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
9-4-2 Adding hosts manually

Users with Modify permission can add hosts to Device Manager. If the Device Manager agent is not installed on a host, you need to manually add the host to the hosts managed by Device Manager. When you add a host manually, specify its host name and WWNs (or iSCSI names). You can use the host name and WWNs to secure LUNs that use the WWNs or iSCSI names of the added host. NOTE: You cannot add more than one host at the same time. Add each host individually. To add a host to Device Manager: 1. In the Explorer menu, select Resources and then Hosts. 2. In the application area, click the Add Host button. The Add Host dialog box appears (see Figure 9-2).
Figure 9-2 Adding a hostentering the name
178
Performing host operations Enter the name for the new host using a maximum of 50 bytes. The host name is not casesensitive. It may include spaces, but cannot consist only of spaces. Leading or trailing spaces are discarded. You can use the following characters: A-Z a-z 0-9 - _ . @ NOTE: You cannot use the same host name as that of a mainframe host that is registered to Device Manager. Confirm the name of mainframe hosts by using the Device Manager CLI (the information about mainframe hosts is not displayed in the web client). For details on how to check a mainframe host name, see the HP StorageWorks XP Command View Advanced Edition software Device Manager CLI user guide. 3. Register a WWN or iSCSI name for the new host. You must register one or more WWNs or iSCSI names using either of the following methods:
Click the appropriate Add button, and then enter the WWN or iSCSI name in the dialog
box that appears. Repeat this operation for each WWN or iSCSI name that you want to register. You cannot register WWNs or iSCSI names that are already registered. To enter WWNs, use the following format: XX.XX.XX.XX.XX.XX.XX.XX (XX: two-digit hexadecimal number) You can omit periods. To enter iSCSI names, use either the iqn or eui format. The entry is not casesensitive. iqn format Enter a character string of up to 223 bytes that begins with iqn.. You can use the following characters: A to Z, a to z, 0 to 9, ., -, and : Specifying only iqn. is not permitted. eui format: Enter a 20-byte character string beginning with eui.. You can use the following characters: 0 to 9, A to F, a to f
Click the Select button, which displays either the Select WWNs dialog box (see Figure
9-3 ) or the Select iSCSI Names dialog box. These dialog boxes display a list of WWNs or iSCSI names that are used as LUN security and that are not registered for any host. From the displayed list, select either the WWNs or the iSCSI names you want to register for the host that you are adding. If the WWNs or iSCSI Names you are registering are used as LUN security, the LUN security can be inherited. You do not need to set LUN security again.
179
Figure 9-3 Add HostSelect WWNs 4. When you have finished adding WWNs or iSCSI Names, review the information on the Add Host dialog box.Click the OK button to add the host or the Cancel button to cancel your request. If your attempt to add a host fails, an error message is displayed. You can re-execute the operation by clicking the Back button to return to the Add Host dialog box.
9-5 Viewing host properties and storage information

All Device Manager users can view host properties and detailed information for the volumes (storage) allocated to each host. To view the host properties and detailed information for the volumes allocated to that host: 1. In the Explorer menu, select Resources and then Hosts, then, expand the Hosts object tree in the navigation area. 2. In the navigation area, select the host for which you want to view information. In the application bar area, the following buttons are displayed:
Modify Properties button (see section 9-6 ) Remove Host button (see section 9-10 )
In the host-name subwindow in the application area, the following properties are displayed for the selected host: Name, IP address, Capacity (total capacity of storage (volumes) allocated to the host), Type (host type). IMPORTANT: If you select an external port displayed under the External Array Nodes object tree in the navigation area, the Remove Host button and IP address are not displayed. NOTE: For a host that uses Fibre Channel for the interface of the internal hard disk, the internal interface WWNs are displayed in addition to the WWNs of the host bus adapter used for the external connection. You can select the following operations: Add Like Storage (see section 9-7 ), Add Storage (see section 9-7 ), Remove Storage (see section 7-6-5 ), Move Storage, Refresh (see section 9-8 ). 180
Performing host operations Add Like Storage, Remove Storage and Move Storage are displayed when storage (volumes) is allocated to the selected host. Refresh is displayed when the Device Manager agent is installed in the selected host.
If storage is allocated to the selected host, the application area lists the volumes that the
host can use. This area also displays the LDEV number, LDEV type, and path for each volume. NOTE: For XP24000/XP20000, a value in the range from 0 to 2,047 can be set for a LUN. For XP12000/XP10000/SVS200, a value in the range from 0 to 1,023 can be set for a LUN. However, since the range of LUNs that the host can recognize varies depending on the OS, the host might not recognize the LUN set in XP24000/XP20000 or XP12000/XP10000/SVS200. NOTE: When LDEVs of multiple storage subsystems are allocated to the selected host, if you sort the list of volumes by LDEV, the LDEVs will be sorted for each storage subsystem. The application area also displays buttons for operating copy pairs and starting other applications.
If copy pairs are managed together as batches: The Replication Management Console
drop-down list shows the hosts that centrally manage copy pairs and meet the requirements. Also, you can manage copy pairs from the application area by using the buttons for operating copy pairs (the Create Pair, Modify Pair, Delete Pair, and View Pair buttons). NOTE: The Create Pair, Modify Pair, and Delete Pair buttons do not appear when you have logged in to Device Manager as a user with only View permission.
If copy pairs are not managed together as batches: When the selected host meets the
copy pair requirements (see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide) and you are managing one or more copy pairs, you can manage copy pairs by using the buttons for managing copy pairs (the Create Pair, Modify Pair, Delete Pair, and View Pair buttons). NOTE: The Create Pair, Modify Pair, and Delete Pair buttons do not appear when you have logged in to Device Manager as a user with only View permission.
If HDLM is installed on the selected host: When the Device Manager agent and HDLM
are installed on the selected host, the application area displays the Dynamic Link Manager button for launching HDLM. For details on launching HDLM, see sections 4-2 and section 5-6-1 , and see the HDLM user documentation. NOTE: To launch HDLM so that they launch displaying a specific volume path, select the desired volume path in the Show Propertieshost-name subwindow and then select the Dynamic Link Manager button. You can select only one volume path. For details about the selectable volume types, see the part describing the devices that HDLM can manage in the HDLM user documentation. NOTE: If a volume you know is allocated to the selected host does not display on the updated View Host Properties window, it could be because Device Manager agents on more than one host recognize the volume, or because the last updated Device Manager agent is not on the current host. If this is the case, click the link on the LDEV column to open the Detailed Information window. 3. To view detailed information for a specific volume allocated to the selected host, select the desired LDEV to open the Detailed InformationLDEV-number dialog box. For details on the information displayed on this dialog box, see section 7-6-1 .
181
9-6 Modifying host properties

Users with Modify permission can modify the existing host properties as needed. To modify the properties of a host: 1. In the Explorer menu, select Resources and then Hosts. Then, expand the Hosts object tree in the navigation area. 2. In the navigation area, select the host for which you want to modify the properties. 3. In the application bar area, click the Modify Properties button. The Modify Properties-hostname window for the selected host is displayed (see Figure 9-4).
Figure 9-4 Modifying host properties 4. Modify the host properties as needed in the Modify Properties window. Note that you cannot modify a WWN or iSCSI name when an external port is selected.
To rename the host:

Edit the name in the Name field. The host name can contain a maximum of 50 bytes and may include spaces. Leading or trailing spaces are discarded. You can use the following characters: A-Z a-z 0-9 - _ . @ The host name is not case sensitive, which means that, for example, if "HOST1" is already registered, a new host name cannot be "host1". You cannot use the same host name as that of a mainframe host that is registered to Device Manager. To confirm the name of mainframe hosts, use the Device Manager CLI. For details on how to check a mainframe host name, see the HP StorageWorks XP Command View Advanced Edition software Device Manager CLI user guide.
To remove WWNs or iSCSI names, select the WWNs or iSCSI names that you want to
remove from the list, and then click the Remove button. Note, however, that you cannot remove all of the WWNs or iSCSI names. To remove the last WWN or iSCSI names, you must remove the host (see section 9-10 ). If the WWNs or iSCSI names you are removing are used as LUN security, select the Modify LUN Security option to clear the LUN security setting of the storage assigned to the host 182
Performing host operations via the WWNs or iSCSI names you are removing. If you do not select the Modify LUN Security option, the WWNs or iSCSI names are still disassociated from the host, but the LUN security of the storage is not cleared.
To register WWNs or iSCSI names for the host, perform one of the following operations: Click the appropriate Add button, and then enter the WWN or iSCSI name in the dialog
box that appears. Repeat this operation for each WWN or iSCSI name you want to register. You cannot register WWNs or iSCSI names that are already registered. To enter WWNs, use the following format: XX.XX.XX.XX.XX.XX.XX.XX (XX: two hexadecimal digits) You can omit periods. To enter iSCSI names, use either the iqn or eui format. The entry is not casesensitive. iqn format Enter a character string of up to 223 bytes that begins with iqn.. You can use the following characters: A to Z, a to z, 0 to 9, ., -, and : Specifying only iqn. is not permitted. eui format: Enter a 20-byte character string beginning with eui.. You can use the following characters: 0 to 9, A to F, a to f
Click the Select button, which displays either the Select WWNs (see Figure 9-3 ) dialog
box or the Select iSCSI Names dialog box. These dialog boxes display a list of WWNs or iSCSI names that are used as LUN security and that are not registered for any host. From the displayed list, select either the WWNs or the iSCSI names you want to register for the host that you are adding, and then click the OK button. Select the WWNs or iSCSI names you want to register for the host and then click the OK button. The LUN security is inherited and does not need to be set again. To register WWNs or iSCSI names for the host to which storage is assigned, select the Modify LUN Security option and change so that LUN security setting of the storage that is assigned to the host can be changed. 5. When you are finished editing the host properties, check the information set in the Modify Propertieshost-name window. If the entered information is correct, click the OK button to save your changes, or click the Cancel button to cancel your request to modify the host properties. The windows displayed depend on which properties you modified in the Modify Properties host-name window and which options you selected when you selected the Modify LUN Security option (in step 4). When the Modify LUN Security option is selected
When you register a WWN or an iSCSI name for the host to which the storage is
assigned, the Modify Propertieshost-name dialog box (LUN List) is displayed. Go to step 6
If you are deleting a WWN or an iSCSI name that was used as LUN security, the Modify
PropertiesConfirmation dialog box appears. In the dialog box, a list of storages whose LUN security is to be released is displayed. If you select Yes, the LUN security used for the WWN or an iSCSI name that is to be deleted will be released. Go to step 7.
For all other cases, the Modify PropertiesConfirmation dialog box appears. The LUN
security for a path assigned to the host will not be changed. Go to step 7. When the Modify LUN Security option is not selected
183
The Modify PropertiesConfirmation dialog box appears. The LUN security for a path
assigned to the host will not be changed. Go to step 7. 6. Review the information displayed in the Modify Propertieshost-name dialog box (LUN List). The dialog box lists the storage assigned to the host (see Figure 9-5).
Figure 9-5 Modifying host propertiesselecting LUN security changes If necessary, select the check box of the storage for which you want to use the new WWN or iSCSI name that you are registering as LUN security. If you click the OK button, the Modify PropertiesConfirmation dialog box appears. In this dialog box, a list of storages whose LUN security is to be modified is displayed. NOTE: For XP24000/XP20000, XP12000/XP10000/SVS200, XP1024/XP128, if you change the LUN security settings for storage in the host storage domain, the change applies to all storage in the same host storage domain. If the storage selected in the Modify Propertieshost-name dialog box (LUN List) belongs to the host storage domain, a list of the storage that will be affected by the changed LUN security setting is displayed. Click the OK button to change the LUN security setting for all affected storage. The Modify PropertiesConfirmation dialog box appears, displaying a list of storages whose LUN security is to be modified. Click the Cancel button to cancel modification of host properties and return to the Show Propertieshost-name dialog box. 7. Confirm the information displayed in the Modify PropertiesConfirmation dialog box. Click the OK button to modify the host properties. Click the Cancel button to cancel modification of host properties. If your attempt to modify host properties fails, an error message is displayed. You can reexecute the operation by clicking the Back button to return to the Modify Properties Confirmation dialog box.
184
NOTE: If you rename the host with the Device Manager agent installed, performing one of the following actions causes both the new name host and old name host to be displayed in the web client host management window. Executing the HiScan command Restarting the Device Manager agent Refreshing the host Delete the old name host, and then refresh the storage subsystem. If you do not delete the old name host, the information about the volumes managed by that host might be displayed incorrectly or you might not be able to use a copy pair.
9-7 Adding storage from host management

Users with Modify permission can add storage to a logical group. To add storage to a logical group: 1. In the Explorer menu, select Resources and then Hosts. Then. 2. Expand the Hosts object tree in the navigation area. 3. In the navigation area, select a host. Perform either of the following operations:
To select a path and logical group to be set for the storage you are adding: In the host-name subwindow displayed in the application area, click the Add Storage
button. A dialog box for selecting a logical group appears.
In the displayed dialog box, select the logical group you want to add the storage to and
then click the OK button. The Add Storage (STEP: Define Host/Port Connections) dialog box appears and the Add Storage wizard starts. For the operations you perform in this dialog box and subsequent tasks, see step 6 and following in section 7-6-2 .
To set a path for the storage you are adding, with the same port and LUN security as
those of the storage assigned to the host, and add the storage to the same logical group: In the host-name subwindow, select a path of LDEVs, and then click the Add Like Storage button. The Add Storage (STEP: Allocate Storage) dialog box appears, and the Add Storage wizard starts. If you use this procedure to add storage, you can select no more than 16 paths at a time. If you select multiple paths, the following conditions must be met:
The paths of LDEVs you select must belong to the same storage subsystem Duplicate paths for the same port, host storage domain, or host must not be included.
For the operations performed in this dialog box and subsequent tasks, see step 8 onward in section 7-6-2 .
9-8 Updating (refreshing) host information

Users with Modify permission can update the host information reported by the Device Manager agent. When you update host information, Device Manager updates the information displayed in the Last Updated, % Used, and File System fields for all storage allocated to the selected host. Device Manager also updates the copy status for the volumes that are managed by the selected host and paired by XP Business Copy Software, XP Snapshot, and XP Continuous Access Software. For details about the system configuration for displaying information about XP Business Copy Software, 185
Performing host operations XP Snapshot, and XP Continuous Access Software, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. NOTE: To update host information, Device Manager agent must be installed on the host.
To update host information from the host-name subwindow: 1. In the Explorer menu, select Resources and then Hosts, then, expand the Hosts object tree in the navigation area. 2. Click the Refresh button in the host-name subwindow. The Refresh HostConfirmation window opens. NOTE: The View Pair Information window also provides access to the update host information function. To select a host performing batch management of pairs, select the target host from the Replication Management Console drop-down list. Then, in the View Pair Information window, click the Refresh button. The Refresh HostConfirmation window opens 3. Check the information in the Refresh HostConfirmation window. If the information is correct, click the OK button to update the host information; otherwise click the Cancel button to cancel your request to modify the host. You are notified when the operation is complete. CAUTION: If a copy pair for XP Business Copy Software or XP Snapshot for XP12000/XP10000/SVS200 is detected while host information is being updated, the Copy Type field for that copy pair is left blank. In this case, you must update the storage subsystem information. For details on updating the storage subsystem information, see section 10-1-4 . CAUTION: When you update the host information, the status of the copy pairs managed by the host is updated, but the modification of the configuration definition file is not reflected. In this case, you must update the storage subsystem information. For details on updating the storage subsystem information, see section 10-1-4 . For details on the configuration definition file, see the XP RAID Manager documentation.
9-9 Managing copy pairs

Users with Modify permission can manage XP Business Copy Software, XP Continuous Access Software, and XP Continuous Access Journal Software copy pairs. The copy pair operations include:
Creating copy pairs (see section 9-9-1 ) Modifying copy pairs (see section 9-9-2 ) Deleting copy pairs (see section 9-9-4 )
NOTE: You cannot create, change, or delete a copy pair of XP Snapshot from the host-name subwindow. If you want to create, change, or delete a copy pair of XP Snapshot, perform the operation from Physical View. NOTE:. For details on the host and storage subsystem requirements for managing copy pairs, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide. For details on requirements of P-VOLs and S-VOLs that make up the copy pairs, see section 4-3 NOTE: When permitting a user assigned to a user-defined resource group to perform copy pair operations, assign the following to the resource group of that user: a host fulfilling the conditions required for performing copy pair operations, and a command device recognized by that host.
186
9-9-1 Creating copy pairs

NOTE: Make sure that LDEVs are formatted before creating a copy pair. You cannot specify an unformatted LDEV to create a copy pair. The following methods can be used to check whether the LDEVs are formatted: For XP24000/XP20000 or XP12000/XP10000/SVS200 in which the functionality to create LDEVs
separately from the formatting of LDEVs is enabled: Use XP Remote Web Console to make sure that the statuses of the LDEVs to be used are Normal.
For XP24000/XP20000 or XP12000/XP10000/SVS200 in which the functionality to create LDEVs

separately from the formatting of LDEVs is disabled, or for XP1024/XP128, and XP512/XP48: LDEVs are formatted by default, so no confirmation is required
Users with Modify permission can create XP Business Copy Software, XP Continuous Access Software, and XP Continuous Access Journal Software copy pairs. CAUTION: When the create copy pair operation is performed, the data on the LDEV that will become an S-VOL will be lost. You must back up any data and make sure the LDEV that will become an S-VOL is no longer in use before creating a copy pair. NOTE: Before creating XP Continuous Access Journal Software pairs, you must set the journal volume and journal group, which you can do by using Physical View of XP24000/XP20000 or XP12000/XP10000/SVS200. For details about Physical View, see section 10-2 . NOTE: XP Continuous Access Journal Software (Resync) is a copy type that is used in the 3DC Multi-Target configuration. You can select this copy type only for XP12000/XP10000/SVS200. In a 3DC Multi-Target configuration, an XP Continuous Access Synchronous Software copy pair and XP Continuous Access Journal Software copy pair that use the same volume for their P-VOL are created. In a 3DC Multi-Target configuration, if you create a new XP Continuous Access Journal Software copy pair whose P-VOL is the existing XP Continuous Access Synchronous Software SVOL and whose S-VOL is the existing XP Continuous Access Journal Software S-VOL, select XP Continuous Access Journal Software (Resync) for the copy type. When you create an XP Continuous Access Journal Software (Resync) copy pair, the storage subsystem, to which the XP Continuous Access Synchronous Software P-VOL and XP Continuous Access Journal Software P-VOL in 3DC Multi-Target configuration belong, must also be managed by Device Manager. For details about the 3DC Multi-Target configuration, see the relevant manual for XP Continuous Access Journal Software. NOTE: If you cascade with pairs other than XP Snapshot pairs, first create the copy pair in the upper level. You cannot create the copy pair in the lower level first. For example, suppose you use LDEV1, LDEV2, and LDEV3 to create the pairs of the P-VOL LDEV1 and the S-VOL LDEV2, and also the P-VOL LDEV2 and the S-VOL LDEV3, and then cascade them. In this case, first create the pair of the P-VOL LDEV1 and the S-VOL LDEV2.
To create one or more copy pairs and copy groups: 1. In the Explorer menu, select Resources and then Hosts, then, expand the Hosts object tree in the navigation area. 2. In the navigation area select the host that contains the P-VOL(s) of the copy pair(s) that you want to create. If copy pairs are not managed in a batch management configuration, the selected host will manage copy pairs. If copy pairs are managed in a batch management configuration, select a host that will manage copy pairs from Replication Management Console in the application area. 3. In the application area, select the check box for each volume that will become the P-VOL of a new copy pair to be created.
187
Performing host operations You can only create pairs of one copy type at one time, so make sure to select P-VOLs for one copy type only. In one operation, you can select a maximum of 100 LDEVs. If you want to perform an operation on more than 100 LDEVs, perform the operation multiple times, selecting no more than 100 LDEVs in each operation. 4. Click the Create Pair button to open the Create Pair wizard (see Figure 9-6). If the Create Pair button is not enabled, one or more of the copy pair requirements for the selected host and/or P-VOL(s) have not been met (see section 4-3 ).
Figure 9-6 Creating a pairchoosing pair(s) step 5. Choose Pair(s) Step. The Choose Pair(s) window (see Figure 9-6) displays the selected PVOL(s) in the P-VOL box and enables you to choose the desired copy type and S-VOL(s) for the copy pair(s) to be created. On the Choose Pair(s) window, select the copy type and S-VOL for each pair as follows:
a. In the Copy Type list box, select the desired copy type for pairs that you are creating now.
The following copy types are displayed: XP Continuous Access Synchronous Software, XP Continuous Access Asynchronous Software, XP Business Copy Software, XP Continuous Access Journal Software, or XP Continuous Access Journal Software (Resync). You can select only one copy type for pairs to be created at one time. After you have added one pair to the Copy Pairs box, the Copy Type box will display only that type of pair. b. From the P-VOL box, select the P-VOL of the pair to be created. Only items that satisfy the selected copy type conditions are displayed in the P-VOL column. NOTE: For the StorageWorks XP Disk Array, if you select an XP Business Copy Softwarecontrolled S-VOL to be the P-VOL of a new XP Continuous Access Software-controlled volume pair, the status of the XP Business Copy Software-controlled pair must be Split.
c. In the S-VOL field, click the Select button to open the Select S-VOL window (see Figure
9-7) of the Create Pair wizard.
188
Figure 9-7 Creating a pairselecting S-VOL(s)

d. From the Host list box, select the host for the S-VOL of the pair to be created and then click
the List LDEV button. The Host list box displays the following hosts.
If copy pair management is performed by a batch management configuration:

- Hosts that are not on external ports.
If copy pair management is not performed by a batch management configuration:

- Hosts where the Device Manager agent is installed. - Hosts where XP RAID Manager is installed. - Hosts that recognizes a command device for which LUN security is set up.
e. In the LDEV List box, select the LDEV that you want to set as the S-VOL for the selected P-
VOL and then click the OK button. The LDEV List box displays only the eligible LDEVs. NOTE: When creating an XP Business Copy Software pair in a storage subsystem that is using XP Disk/Cache Partition, do not select an LDEV that belongs to a different SLPR. If you select such an LDEV, the partition storage administrator can no longer manage the storage subsystem.
f.
Verify that the S-VOL field contains the selected LDEV.
If the S-VOL field contains the selected LDEV, click the Add button to add the P-VOL
and S-VOL pair. The Copy PairsP-VOLs and S-VOLs box now displays the pair to be added.
If either the S-VOL or the P-VOL fields are not correct, select the check box for the pair
that you want to click the Remove button.
g. Repeat steps a through f until you have selected all the copy pairs to be created, and then
click the Next button. 6. Define Pair(s) Step. In the Define Pair(s) window (see Figure 9-8), define the parameters for each pair.
189
Figure 9-8 Creating a pairdefining pair(s) step From the View Pair Information, you can view the parameters of existing copy pairs. To view the parameters of the existing copy pairs, select a host that is managing copy pairs you want to view from the Hosts drop-down list, and then click the View button to open a window for viewing copy pair information (see Figure 9-9).
Figure 9-9 Creating a pairviewing pair information NOTE: The displayed host is the host that manages copy pairs. If pair management is performed by a central management method, the host that manages copy pairs centrally is displayed. In the Define Pair(s) window, define the groups and parameters for the copy pairs as follows. After defining the parameters for all copy pairs, select Finish. Group. Select the desired copy group for all copy pairs being created, or create a new group if desired. For details on copy groups, refer to the XP Business Copy Software, XP Continuous
190
Performing host operations Access Software or XP Continuous Access Journal Software manual for the storage subsystem. The following combinations of copy pairs cannot be registered to the same copy group or to an existing copy group.
The LDEVs making up the copy pair are allocated to different hosts. Copy pairs of level 1 and level 2 when using XP Business Copy Software cascade Copy pairs of different copy types StorageWorks XP Disk Array copy pairs Copy pairs of different fence levels XP Continuous Access Journal Software copy pairs registered in different journal groups
To create a new copy group, select the New button, and then use the New Copy Group window (see Figure 9-10) to specify the group name, P-VOL, S-VOL, XP RAID Manager (HORCM) instance name for each host, and port number for the new group. In the Pair Name list, enter the desired name for the pair. The name must not be longer than 31 characters. You can use the following characters to specify the name: A-Z a-z 0-9 - _ . @ If the name is omitted, the following name is automatically set: HCMD-CPxxxx (xxxx: hexadecimal) CAUTION: You cannot use a hyphen (-) at the beginning of the pair name. Fence Level (XP Continuous Access Synchronous Software only). Select the desired fence level (Never, Data, or Status). For details on fence level, refer to the XP Continuous Access Software manual for the storage subsystem. Copy Pace (XP Business Copy Software, XP Continuous Access Software, and XP Continuous Access Journal Software). Select the desired pace for the initial copy operation: Slower, Medium, or Faster for XP Business Copy Software or for XP Continuous Access Journal Software. Select the number of tracks to be copied at one time for the initial copy operation: 1 through 15 for XP Continuous Access Software. The faster the copy pace (15 tracks or faster), the shorter the period of time required for copying. However, a fast copy pace may affect the I/O performance of the storage subsystem (only during the initial copy operation). Journal Group (XP Continuous Access Journal Software only): If you want to register a copy pair to be created into a copy group in which an XP Continuous Access Journal Software copy pair has been registered, for the newly created copy pair, the same journal group number as the number for the already registered copy pair will be displayed. If you want to register the copy pair in a new copy group, you can select the journal group in which you want to register copy pair volumes. After you create a new copy group, the Select button becomes active. Clicking the Select button displays a dialog box for selecting a journal group (see Figure 9-11). From the Journal Group List (P-VOL) list, select a journal group in which a P-VOL is registered. If you selected a journal group in which no P-VOL is registered, select a mirror ID. When you select a journal group in which a P-VOL is to be registered, the sub-journal group candidates of the selected journal group are displayed in the Journal Group List (S-VOL) list. Select the journal group in which the S-VOL is to be registered, and then click the OK button. The pair definition window reappears. NOTE: In one copy group, you can register only XP Continuous Access Journal Software copy pairs that belong to the same journal group. Therefore, when you register multiple copy pairs in the same new copy group, if you select a journal group for one copy pair, that journal group is also set for the other copy pairs.
191
Figure 9-10 Creating a pairdefining a new copy group
Figure 9-11 Selecting a journal group 7. Summary of Changes Step. The Summary of Changes window (see Figure 9-12) displays the requested create pair operation(s) and asks you to confirm the requested operation(s). Review the operation(s) carefully, and click Confirm to confirm the operation(s), or click Cancel to cancel your request. If you need to make any changes, click Back to return to the previous window (s). The Cancel(Output HORCM) button is displayed when the function used to create configuration definition files is enabled. Click the Cancel(Output HORCM) button to create a configuration definition file. For details on how to enable the function to create configuration definition files, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
192
Figure 9-12 Creating a pairconfirmation step 8. Device Manager displays the new S-VOL(s) and warns you that the data on these volumes will be lost. Click the Confirm button to start the requested create pair operation(s), or click the Cancel button to cancel your request to create the pair(s), click the Back button to return to previous window. A system message is displayed when the create copy pair operation(s) is/are complete. Once a copy pair has been created, the initial copy action starts. The copy status of P-VOL and SVOL becomes Copying and then changes to Pair when the initial copy is complete. To update the copy status to the latest information, refresh the host.
9-9-2 Modifying copy pairs

Users with Modify permission can modify the status of XP Business Copy Software, XP Continuous Access Software and XP Continuous Access Journal Software copy pairs. NOTE: The status of XP Continuous Access Journal Software (Resync) copy pairs cannot be changed.
Table 9-3 shows the operations that you can perform to modify a copy pair. For resync and restore operations, you can specify the copy pace. For more information on splitting, resynchronizing, and restoring copy pairs, refer to the XP Business Copy Software, or XP Continuous Access Software manual for your storage subsystem (for example, the XP Business Copy Software User's Guide). NOTE: See section 4-3 for important information on copy pair (e.g., P-VOLs, S-VOLs, SP-VOLs, etc).
193
Table 9-3 Requirements for modify pair operations Target of Operation

Copy group
Operations that can be performed

If one or more copy pairs in the group are in Suspend or Error In LUSE status:
For XP Continuous Access Software and XP Continuous Access Journal Software,

select Resync.
For XP Business Copy Software, select Resync or Restore.

If all copy pairs in the group are in the Split status:

select Resync.

If all copy pairs in the group are in Pair, Copying, or Reverse-Copying status, select Split. Other than above:

select Split or Resync.
For XP Business Copy Software, select Split, Resync, or Restore.

Copy pair If the copy pair is in the Split or Suspended status:

select Resync.

If the copy pair is in Error In LUSE status (for XP Continuous Access Software), select Resync. If the copy pair is in Pair, Copying, or Reverse-Copying status, select Split. Other than above:

select Split or Resync.
For XP Business Copy Software, select Split, Resync, or Restore. NOTE: If you want to change the status of a StorageWorks XP Disk Array XP Business Copy Software copy pair whose S-VOL is a P-VOL for XP Continuous Access Software, the status of the XP Continuous Access Software pair must be "Split". Table 9-4 lists the requirements for performing operations on XP Business Copy Software cascaded pairs (StorageWorks XP Disk Array). The first cascade level is called L1, and the second level is called L2. For example, for the cascaded pairs for LDEV1, LDEV2, and LDEV 3 is: LDEV1 and LDEV2 are the L1 pair, LDEV2 and LDEV3 are the L2 pair, and LDEV2 is an S-VOL for L1 and a P-VOL for L2. Table 9-4 Modifying XP Business Copy Software cascade pairs Operation
Split operation for L1 pair Split operation for L2 pair Resync operation for L1 pair Resync operation for L2 pair
Required Status
L2 pair status must be Pair, Copying, Split, or Suspended. L1 pair status must be Split. L2 pair status must be Pair, Copying, Split, or Suspended. L1 pair status must be Pair, Copying, Reverse-Copying, Split, or Suspended.
194
Table 9-4 Modifying XP Business Copy Software cascade pairs Operation

Restore operation for L1 pair Restore operation for L2 pair
Required Status
L2 pair status must be Pair, Copying, Split, or Suspended. Not allowed.
To modify one or more copy pairs: 1. In the Explorer menu, select Resources and then Hosts. Then, expand the Hosts object tree in the navigation area. 2. In the navigation area, select the host that manages the copy pair(s) you want to modify. If the host selected in the navigation area centrally manages copy pairs, in Replication Management Console in the application area you can change the host that manages the copy pair that you want to modify. 3. Click the Modify Pair button to open the Modify Pair wizard (see Figure 9-13). The window used to select pairs appears.
Figure 9-13 Modifying a pairselect modify pair(s) step NOTE: The displayed host is the host that manages copy pairs. If pair management is performed by a central management method, the host that manages copy pairs centrally is displayed. 4. In the Select Modify Pair(s) window (see Figure 9-13) allows you to select the copy group(s) and/or copy pair(s) for which you want to modify the status. When you are finished selecting copy groups/pairs, click Next. NOTE: You can only perform one type of operation at a time (split, resync, or restore), so make sure to select copy groups/pairs for one operation type only. 5. In the Modify Pair(s) window (see Figure 9-14) select the desired Operation (split, resync, or restore) and Copy Pace for the selected copy group(s)/pair(s). When you are finished selecting the operation and copy pace for the pair(s), select Finish.
195
Figure 9-14 Modifying pair(s) step Operation: Select Split, Resync, or Restore. For requirements on performing the Split, Resync, and Restore operations, see Table 9-3. For requirements on performing Split, Resync, and Restore operations for XP Business Copy Software cascade pairs, see Table 9-4. Copy Pace: Instead of the displayed current value for the copy pace, select the changed value: Slower, Medium, or Faster for XP Business Copy Software, and for XP Continuous Access Journal Software; 1 through 15 for other case. You cannot change the value for the copy pace if split is selected from Operations for XP Continuous Access Software or XP Continuous Access Journal Software. NOTE: If you want to change the status of a StorageWorks XP Disk Array XP Business Copy Software copy pair whose S-VOL is a P-VOL for XP Continuous Access Software, the status of the XP Continuous Access Software pair must be "Split". NOTE: The Copy Pace value does not appear for a copy pair that was created using other management tools (such as XP Remote Web Console or SVP) or that was created by another Device Manager server. If you used another management tool to modify the Copy Pace, the modified value will not be applied and the value set by Device Manager will be displayed. Therefore, use Device Manager to modify the Copy Pace of a copy pair managed by Device Manager. 6. Summary of Changes Step. The Summary of Changes window displays the requested modify pair operation(s) and asks you to confirm the operation(s). If you selected a copy group, ALL PAIRS is displayed for Pair. Review the operation(s) carefully, and click the Confirm button to confirm the operation(s), click the Cancel button to cancel your request. If you need to make any changes, click Back to return to the previous window(s). 7. If you selected the split operation, Device Manager warns you that the data on the S-VOL may not be complete if you split a pair during I/O processing on the P-VOL. Read the warning carefully, and click the OK button if there is no problem, or click the Cancel button to cancel your request to split the pair(s). You are notified when the modify copy pair operation is complete.
9-9-3 Notes on copy pair operations

This section provides information on copy pair operations. Table 9-5 lists items to consider before creating copy pairs.
196
Table 9-5 Items to consider before creating copy pairs Item

Existing copy pair
Description
A copy pair can be created by using storage subsystem management tools such as XP Remote Web Console and SVP. However, there is no HORCM configuration file created for XP RAID Manager control for the copy pair created by the above management tools. Therefore, the status of the copy pair cannot be changed or deleted by using the Device Manager server. To change or delete the status of a copy pair by using the Device Manager server, delete the copy pair by using the appropriate management tool, and then create the copy pair again by using the Device Manager server. Store the configuration definition file for XP RAID Manager in the location predefined by each OS. For details on the storage location of the configuration definition file, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide. It might take some time to add a storage subsystem or refresh operations when both of the following conditions are satisfied:
HORCM configuration file (horcm.conf)
Device Manager agent and XP RAID Manager are installed on the host that the Device
Manager server recognizes.
There is an unused HORCM configuration file on the host, or a lot of unused copy pairs
are defined in the HORCM configuration file. In such a case, disable the unused HORCM configuration file or the unused copy pair definitions in the HORCM configuration file, by using the following methods:
Disabling an unnecessary HORCM configuration file

Set the instance number of the unused HORCM configuration file to the Device Manager agent's property server.agent.rm.exclusion.instance, stop the Device Manager agent, and then restart the Device Manager agent.
Disabling an unused copy pair definitions in the HORCMconfiguration file

Delete the unused copy pair definition in the HORCMconfiguration file, or make the definition a comment line. Central management method HRX intermediate volume When a single host centrally manages the creation, status change, and deletion of copy pairs, disable the command device security functionality on the host that manages the copy pairs. If the command device security functionality is enabled, an LU not recognized by the host cannot be managed by the copy pair. Copy pair information cannot be acquired when the same port is assigned to an open-system volume and an HRX intermediate volume. If the storage subsystem using the copy pair functionality is using an HRX intermediate volume, prepare a dedicated port for the HRX intermediate volume in order to separate the port for the open-system volume.
Table 9-6 provides notes on copy pair operations. Table 9-6 Notes on copy pair operations Item Description
Creating copy When an XP Business Copy Software and XP Continuous Access Software copy pair is pair created for one LU, or when an XP Business Copy Software cascaded copy pair is defined, use different combinations of group names and pair names for each copy pair. When creating a new copy pair, make sure that the pair definition for that LU has not already been defined. If there is an invalid pair definition, delete the corresponding copy pair definition from the HORCM configuration file as necessary. Displaying a copy pace The copy pace value is not displayed for copy pairs created by other management tools such as XP Remote Web Console and SVP, or copy pairs created by another Device Manager server. Also, if you used another management tool to modify the Copy Pace, the modified value will not be applied and the value set by Device Manager will be displayed. Therefore, use Device Manager to modify the Copy Pace of a copy pair managed by Device Manager.
197
Table 9-6 Notes on copy pair operations Item

Cascaded copy pair
Description
When using XP24000/XP20000, XP12000/XP10000/SVS200, XP1024/XP128, and XP512/XP48, the following conditions must be satisfied to operate the cascaded copy pair: The first tier of the cascade is called L1, and the second is L2. For example, when pairs are cascaded in the order LDEV1, LDEV2, and LDEV3, the L1 pair is LDEV1 and LDEV2, and the L2 pair is LDEV2 and LDEV3.
When performing Split operations for the L1 pair:

The L2 pair status must be one of the following: Pair, Copying, Split, or Suspended
When performing Split operations for the L2 pair:

The L1 pair status must be Split.
When performing Resync operations for the L1 pair:

The L2 pair status must be one of the following: Pair, Copying, Split, or Suspended
When performing Resync operations for the L2 pair:

The L1 pair status must be one of the following: Pair, Copying, Reverse-Copying, Split, or Suspended
When performing Restore operations for the L1 pair:

The L2 pair status must be one of the following: Pair, Copying, Split, or Suspended. You cannot perform Restore operations for the L2 pair. LDEV with When a copy pair is created using an LDEV with multiple paths assigned, the Device Manager multiple paths server automatically determines the port for the copy pair volume specified in the assigned HORCMconfiguration file. Device Manager selects the ports in ascending alphabetical order of their names. For example, when the LDEV where the paths via CL1-A and CL2-A are assigned is selected to create a copy pair, CL1-A is specified as the HORCM configuration file. If the path via CL1A is deleted, this copy pair will become inoperable. In such a case, the HORCM configuration file must be edited directly. For details on editing the HORCM configuration file, refer to the HP StorageWorks XP RAID Manager user guide.
198

Error code 7774
Description
Error code 7774 occurs when the Device Manager agent fails to create a HORCM configuration file, start the HORCM instance, or execute the pair creation or status change command. In this case, the error messages output by the web client and their causes are as follows: 1 This Config File could not be modified. Cause 1: The HORCM configuration file could not be created because the Device Manager agent could not recognize the LU specified for the copy pair. Action 1: Update the database by refreshing the storage subsystem or the host. Cause 2: The HORCM configuration file could not be created because the Device Manager agent could not recognize the command device. Action 2: Assign the command device to the host that is running the Device Manager agent, and then refresh the host. 1 2 This HORCM instance could not be started. Detailed message: starting HORCM inst instance-number. HORCM inst instance-number has failed to start. Cause 1: The specified instance port-number is being used by another application. Action 1: Check the usage status of the port numbers by executing the netstat command, and then specify an unused port number. Cause 2: Disk space is insufficient. Each instance requires about 100 KB of free disk space. Action 2: Check the free disk space, and then make secure the required disk space by deleting any unnecessary files. 3 Could not create pair group-name:pair-name. 2 Detailed message: paircreate: [EX_CMDIOE] Control command I/O error Refer to the command log (/HORCM/log123/horcc_japan.log) for details. Cause 1: The maximum number of copy pairs that can be created on the device has been reached. For details on the maximum number of copy pairs, refer to the manual for copy pairs for the storage subsystem. Action 1: Delete any unnecessary copy pairs. Check the number of copy pairs by using SVP or XP Remote Web Console. Cause 2: When using XP Continuous Access Software, the remote path was blocked. Action 2: Check the remote path status by using SVP, XP Remote Web Console, and then release the blockage. 4 The ConfigFile of this instance number does not exist. Cause 1: An inconsistency occurred between the host status and the database of the Device Manager server. Action 1: Update the database by refreshing the storage subsystem and executing HiScan on the target host. If the same error still occurs, restart the Device Manager agent. When the HiScan command is executed on a host that recognizes an LU which the Device Manager server is using to create or delete a copy pair, the pair status displayed in the web client might be incorrect. In such a case, refresh the storage subsystem from the web client. However, the copy pace display is not restored. If the copy pace display is needed, reset the copy pace by changing the copy pair status. The copy status of a copy pair created using a host that is not the host centrally managing copy pairs is not updated, even though the host information is updated, if the host centrally managing copy pairs does not recognize the copy pair volumes. In this case, refresh the storage subsystem that has the copy pair volume for which you want to change the copy status.
HiScan command
Updating information for a host that manages copy pairs centrally
199

Configuration definition file (horcm.con f)
Description For the cases listed below, refresh the storage subsystem to which the copy pair volume
coded in the configuration definition file belongs. When the storage subsystem is refreshed, the contents of the configuration definition file are applied to Device Manager. When the contents of an XP RAID Manager configuration definition file, which was created by Device Manager, were changed When you want to apply the contents of an XP RAID Manager configuration definition file, which was not created by Device Manager, to Device Manager If you want to apply, to Device Manager, the contents of an XP RAID Manager configuration definition file that was not created by Device Manager, specify the HORCM_CMD parameter in the configuration definition file. For details on the syntax of the parameter, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide. 3
An error might occur when attempting to create a copy pair by using an LU that satisfies the following conditions:
The LU is assigned to the CL1-A port or LUN0. The host used for creating the copy pair recognizes the above path.
In such a case, either assign a different port to the LU or assign a LUN other than LUN0, and then re-create the copy pair. 2 The [EX_xxxxx] displayed in the detailed message is an XP RAID Manager error message. For details on XP RAID Manager error messages, refer to the HP StorageWorks XP RAID Manager user guide. If the situation does not improve, even after performing the above operations, contact the Support Center. 3 You can also use the property file for the Device Manager agent to apply the contents of the configuration definition file to Device Manager. When you use the property file for the Device Manager agent to specify this setting, the specified configuration definition file will be optimized. For details about optimizing the configuration definition file, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
Table 9-7 provides notes on managing the host. Table 9-7 Notes on managing the host Item
Shutting down the host or stopping the Device Manager agent HORCM instance
Description
When operating a copy pair, shutting down the host that recognizes that copy pair, or stopping the Device Manager agent, will cause the copy pair operation to time out within 15 minutes. Make sure that the host or Device Manager agent restarts, and then perform the copy pair operation again. The HORCM instance that was started by the Device Manager agent in Windows cannot be fully operated, including finishing. To avoid this, the Device Manager agent HBsA Service permissions must be changed from local system to administrator. When you want to operate the HORCM instance, change the Device Manager agent HBsA Service permissions as shown above.
200
Table 9-7 Notes on managing the host Item Description
Changing the host's If a copy pair is created when ipaddress is specified for IP address or host server.horcmconfigfile.hostname in the server.properties file, changing name the host's IP address will make the copy pair inoperable. If a copy pair is created when hostname is specified for server.horcmconfigfile.hostname in the server.properties file, changing the host name will make the copy pair inoperable. In such a case, refresh the storage subsystem by following this procedure: 1 Modify the configuration definition file on the applicable host 2 Restart the Device Manager agent on the applicable host 3 Modify the HORCM configuration file on the host of the copy pair source against the applicable host of the copy pair destination. For details on server.horcmconfigfile.hostname properties, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. AIX host For AIX hosts, the OS stores disk management information on the volume. Therefore, when P-VOL and S-VOL are assigned to the same host, the disk management information stored on the volume is copied from P-VOL to S-VOL, and the OS might not be able to recognize the volume as normal. In such a case, execute the recreatevg command to re-create the volume group. In such a case, execute the recreatevg command to re-create the volume group.When using Dynamic Link Manager, execute the dlmrecreatevg command to re-create the volume group.For details on these commands, see the part describing the devices that HDLM can manage in the HDLM user documentation.
Refreshing the Performing discovery or refresh operations for the storage subsystem will update storage subsystem information about the HORCM configuration file and information about copy pairs recognized by each host. If the system cannot communicate normally with the host during the operation, the information about the copy pair recognized by that host and information about the HORCM configuration file might be lost. In such a case, the Modify Pair button in the host management window is not displayed and the information about the copy pair recognized by the host is not displayed. Check the host status, perform any necessary operations, and then refresh the storage subsystem. For details on checking the host status, see section 9-5 . When buttons for If the copy pair functionality (such as the Create Pair button) is not displayed, perform copy pair the following operations: functionality are not 1 Note that XP RAID Manager must be installed on the host managed by Device displayed Manager. 2 3 4 5 6 Make sure that the host recognizes the command device. Make sure that the host recognizes the LDEV that the host can manage as a pair. Make sure that the command device is not mounted. Restart the Device Manager agent. Refresh the storage subsystem.
9-9-4 Deleting copy pairs

Users with Modify permission can delete XP Business Copy Software, XP Continuous Access Software, and XP Continuous Access Journal Software copy pairs. When a copy pair is deleted, the P-VOL and S-VOL are changed to "Simplex" status, and the storage subsystem stops replicating the P-VOL updates on the S-VOL. For details on deleting copy pairs, refer to the XP Continuous Access Software, or XP Business Copy Software manual for your storage subsystem. To delete one or more copy pairs:
201
Performing host operations 1. In the Explorer menu, select Resources and then Hosts. Then, expand the Hosts object tree in the navigation area. 2. In the navigation area select the host that manages the copy pair(s) that you want to delete. If the host selected in the navigation area centrally manages copy pairs, in Replication Management Console you can change the host that manages the copy pairs that you want to delete. 3. Click the Delete Pair button to open the Delete Pair wizard (see Figure 9-15). The window used to select pairs appears.
Figure 9-15 Deleting a pairselect delete pair(s) step NOTE: The displayed host is the host that manages copy pairs. If pair management is performed by a central management method, the host that manages copy pairs centrally is displayed. 4. Select Delete Pair(s) Step. The Select Delete Pair(s) window (see Figure 9-15) enables you to select the copy group(s) and/or copy pair(s) that you want to delete. When you are finished selecting groups/pairs, click the Next button. 5. The Summary of Changes window showing the requested delete pair operation(s) and asking you to confirm the operation(s). If you selected a copy group, ALL PAIRS is displayed for Pair. Review the operation(s) carefully, and click the Confirm button to confirm the operation(s), click the Cancel button to cancel your request. If you need to make any changes, click Back to return to the previous window (s). 6. Device Manager warns you that the data on the S-VOL may not be complete if you delete a pair during I/O processing on the P-VOL. Read the warning carefully, and click OK if there is no problem, or click Cancel to cancel your request to delete the pair(s). You are notified when the delete copy pair operation(s) is/are complete.
9-10 Removing a host

Users with Modify permission can remove an existing Device Manager host. Note that you cannot delete the external port. You can remove multiple hosts together in one operation as required, or you can check the host properties before removing each host from the system.
202
9-10-1 Removing multiple hosts in one operation

When you remove multiple hosts registered with Device Manager in one operation, removing the host does not clear the LUN security. To remove multiple hosts from Device Manager in one operation: 1. In the Explorer menu, select Resources and then Hosts. Then, select the Hosts object in the navigation area. 2. In the sortable table, select the check boxes of the hosts you want to remove (you can remove a maximum of 40 hosts in one operation), and then click the Remove Hosts button in the application area. 3. A dialog box for confirming that you want to remove the hosts is displayed. Check the hosts listed in the sortable table, and then click the OK button to remove them. To cancel the action, click the Cancel button. A message is displayed when the operation is complete.
9-10-2 Removing hosts one by one

When removing hosts registered with Device Manager one by one, you can check the host properties before removing each host. You can choose whether to clear LUN security when you remove a host. To remove hosts one by one from Device Manager: 1. In the Explorer menu, select Resources and then Hosts. Then, expand the Hosts object tree in the navigation area (see Figure 9-1). 2. In the navigation area, select a host-name. The host-name subwindow appears in the application area. 3. To remove the selected host, click the Remove Host button in the application bar area. A dialog box confirms your removal of the host. If a WWN of the host you are removing is used as LUN security, a list of the storage subsystems that have LUN security is displayed. 4. To remove the host and clear the set LUN security, click the Remove LUN Security button. If you do not select this option, the host will be removed, but the LUN security will persist. 5. Click the OK button to remove the host. To cancel the operation, click the Cancel button. A message is displayed when the operation is complete.
9-11 Applying WWN information when replacing host bus adapters

This section describes how to apply information of a host WWN to Device Manager when you replace the host bus adapter of a host managed by Device Manager. To apply WWN information: 1. Modify the properties of a host that will have its host bus adapter replaced. When you replace a host bus adapter used for Fibre Channel, add a WWN. For instructions for adding the WWN, see section 9-6 . 2. Stop the host and physically replace the host bus adapter. 3. Start the host. The host can access the LUN associated with the host via the new host bus adapter. 4. Modify the properties of the host that had its host bus adapter replaced. From the host properties, delete the WWN name for the detached host bus adapter. For instructions for removing the WWN, see section 9-6 . 203
Performing host operations The new WWN is set for LUN security associated with the host.
204
Performing storage subsystem operations
10 Performing storage subsystem operations

Users assigned to the All Resources resource group can manipulate storage subsystems. Users with Modify permission can add storage subsystems to Device Manager, remove storage subsystems from Device Manager, and edit storage subsystem properties. Users with only View permission can only view information about storage subsystems. Users assigned a user-defined resource group cannot manipulate storage subsystems. This chapter describes Device Manager storage subsystem operations in the following sections:
Overview of storage subsystem operations (see section 10-1 )
Viewing a list of storage subsystems (see section 10-1-1 ) Adding a storage subsystem (see section 10-1-2 ) Viewing and editing storage subsystem properties (see section 10-1-3 ) Performing a refresh operation (see section 10-1-4 ) Adding a new IP address (see section 10-1-5 ) Removing a storage subsystem (see section 10-1-6 ) Viewing information for XP24000/XP20000 (see section 10-2-1 ) Viewing information for XP12000/XP10000/SVS200 (see section 10-2-2 ) Viewing information for XP1024/XP128 (see section 10-2-3 ) Viewing information for XP512/XP48 (see section 10-2-4 ) Viewing LDEV information (see section 10-2-5 ) Configuring the ports (XP1024/XP128 and XP512/XP48) (see section 10-3-1 ) Managing LUN groups (see section 10-3-2 ) Managing WWN groups (see section 10-3-3 ) Configuring Fibre Channel adapters (XP1024/XP128 and XP512/XP48) (see section 103-4 ) Allocating storage (adding volume paths) (see section 10-4-1 ) Unallocating storage (removing volume paths) (see section 10-4-2 ) Creating an LDEV (see section 10-4-3 ) Deleting an LDEV (see section 10-4-4 ) Setting or canceling a command device (see section 10-4-5 )
Physical View operations (see section 10-2 )
Port operations (see section 10-3 )
LDEV operations (see section 10-4 )
10-1 Overview of storage subsystem operations

Users assigned to the All Resources resource group can manipulate storage subsystems. Available operations depend on the permission set for the user. The following describes available operations for each permission:
Users with Modify permission can add storage subsystems to Device Manager, remove storage subsystems from Device Manager, and edit storage subsystem properties. Users with View permission can view information about storage subsystems.
Users assigned a user-defined resource group cannot manipulate storage subsystems. 205
Performing storage subsystem operations Device Manager storage subsystem operations include:
Viewing a list of storage subsystems (see section 10-1-1 ) Adding a storage subsystem (see section 10-1-2 ) Viewing and editing storage subsystem properties (see section 10-1-3 ) Performing a refresh operation (see section 10-1-4 ) Adding a new IP address (see section 10-1-5 ) Removing a storage subsystem (see section 10-1-6 )
NOTE: If you used a subsystem-management tool other than Device Manager to change the user ID, password, or IP address that were specified when the storage subsystem was added, you need to update the information registered in Device Manager. (See section 10-1-3 and 10-1-5 ) NOTE: If you change the storage subsystem configuration, you should back up the new information. For details, refer to the manual for the corresponding storage subsystem.
10-1-1 Viewing a list of storage subsystems

Users assigned to the All Resources resource group can view a list of storage subsystems. To display a list of storage subsystems managed by Device Manager, in the web client Explorer menu, select Resources and then Subsystems. When the Subsystems object is selected in the navigation area, the application bar area displays the Add Subsystem button (see section 10-1-2 ), and the application area displays the list of storage subsystems. You can view the information about a storage subsystem by selecting the link for the storage subsystem name in this list. When a storage subsystem is selected in the navigation area, the application bar area displays the following operations: When a storage subsystem is selected in the navigation area, the application bar area displays the buttons to execute the following operations:
Modify properties (see section 10-1-3 ) Refresh (see section 10-1-4 ) LUN Scan (see section 8-3 ) Remove subsystem (see section 10-1-6 )
When a storage subsystem is selected in the navigation area, the subsystem-name subwindow in the application area displays the properties of the storage subsystem (see section 10-1-3 ). NOTE: The total size (configured capacity) that is displayed is not the total size of the physical disk. It is the total available disk size, which means the total of the sizes of all logical devices on the machine. The total available disk size is increased or decreased by creating or deleting logical devices.
10-1-2 Adding a storage subsystem

Users with Modify permission who are assigned to the All Resources resource group can add a storage subsystem to Device Manager. When you add a storage subsystem, Device Manager performs the following operations. Be aware that the processing to add a the subsystem is complex and might take a while.
Locates the storage subsystem. Performs an initial configuration check, and then groups for each storage subsystem under the All Storage object or the My Storage object.
206
Creates the Open-Allocated, Open-Unallocated, and Open-Reserved groups under the groups for each subsystem Device Manager lists the LDEVs or LUs, with paths allocated on open volumes, in the OpenAllocated group, and lists the LDEVs or LUs without paths in the Open-Unallocated group. In the Open-Reserved group, a list of open volumes on which paths cannot be allocated is displayed. Mainframe volumes are displayed in the Mainframe-Unspecified group.
NOTE: Add storage subsystems individually. Multiple storage subsystems cannot be added concurrently. NOTE: Processing to add a storage subsystem is complex and might take a while. NOTE: When adding a storage subsystem, you need use a storage subsystem-management tool to set a user ID used in Device Manager. We recommend that you use different user IDs for the user ID used in Device Manager and for the user ID used for storage subsystem-management tool operations. NOTE: Note the following points when you manage an external subsystem under Device Manager while you are using XP External Storage Software: If an external subsystem is the only object that has been added to Device Manager, Device Manager is
unable to recognize that the added external subsystem is connected as an external subsystem. When an external subsystem has been added to Device Manager, make sure that a storage subsystem that uses XP External Storage Software has also been added.
After you add an external subsystem to Device Manager to which a storage subsystem that uses XP
External Storage Software has been added, you must perform a refresh operation on the storage subsystem. This enables Device Manager to acquire information to recognize the external subsystem.
To add a storage subsystem to Device Manager: 1. In the Explorer menu, select Resources, and then Subsystems, and then click the Add Subsystem button in the application bar area. The Add Subsystem window is displayed. 2. In the Add Subsystem window, select the type of storage subsystem to be added, (for example, XP12K/10K/SVS200). The information depends on the type of storage subsystem selected. 3. Enter the IP address(es) or host name of the storage subsystem. Enter a maximum of 50 bytes, using the following characters: A-Z a-z 0-9 - _ . @ / : 4. Enter the information required for Device Manager to access the storage subsystems.
For XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, enter the user

ID and password set in XP Remote Web Console.
For the XP512/XP48, enter the SNMP community name (such as public) for the storage
subsystem. You can enter a maximum of 15 bytes, using the following characters: A-Z a-z 0-9 5. When you finish entering the information for the new storage subsystem, click OK button to add the storage subsystem. Device Manager searches through storage subsystems in the network and detects the specified storage subsystem. You can perform other operations while this process is in progress, but you cannot add other storage subsystems. A message is displayed when the add storage subsystem operation is completed. The name of the new storage subsystem appears in the following format: storage-subsystem-type@storage-subsystem-IP-address for example: XP10000@10.208.116.105
207
10-1-3 Viewing and editing storage subsystem properties

Users assigned to the All Resources resource group can manipulate storage subsystem properties. Available operations depend on the permission set for the user. The following describes available operations for each permission:
Users with Modify permission can edit storage subsystem properties. Users with View permission can view information about storage subsystem properties.
NOTE: Device Manager uses the user ID and password set in a storage subsystem to access that storage subsystem. Specify, for the storage subsystem properties in Device Manager, which user ID and password to be used to access that storage subsystem. We recommend that you specify a user ID different from the one used for storage subsystem management tool operations. If the user ID and password used by Device Manager to access a storage subsystem are changed, edit the storage subsystem properties for that storage subsystem in Device Manager.
To view and edit the properties of a storage subsystem: 1. In the Explorer menu, select Resources and then Subsystems, and then select the desired storage subsystem in the navigation area. The subsystem-name subwindow displays the following storage subsystem properties the application area:
Name: The name of the storage subsystem Type: The type (vendor model) of the storage subsystem (for example, XP128) Serial number (for other than XP24000/XP20000) or DKC (for XP24000/XP20000): the
serial number of the storage subsystem
LDKC#0 (for XP24000/XP20000): logical DKC serial number for logical DKC number 0 LDKC#1 (for XP24000/XP20000): logical DKC serial number for logical DKC number 1 IP Address (StorageWorks XP Disk Array): The IP address of the storage subsystem Microcode DKC: The microcode level of the disk controller Microcode SVP (StorageWorks XP Disk Array): The microcode level of the service processor (SVP) of the physical disks the total available disk size, that is, the total of the sizes of all logical devices on the machine. The configured capacity increases or decreases when logical devices are created or deleted.
Configured Capacity: The configured capacity of the storage subsystem, not the total size
Actual Capacity: The total physical capacity of the LDEVs in the storage subsystem Total Cache: The total cache capacity of the storage subsystem Last Refreshed: The last time the storage subsystem was refreshed or added to Device
Manager
Alerts: The number of red vertical bars indicates the number of alerts for the storage
subsystem. When you click a red vertical bar, a list of the alerts is displayed (see section 5-4 for details on alerts). NOTE: Clicking the Physical View button opens the Physical View dialog box for the selected storage subsystem (see section 10-2 ). NOTE: If you are using the URLLink feature in Device Manager, a URLLink-name button appears (see section 5-6-8 ). Clicking the URLLink-name button launches a Web application specified using the URLLink feature. If you are logged in as a user who has View permission only, this button is inactive. NOTE: When XP Remote Web Console is installed on XP1024/XP128, the XP Remote Web Console button is displayed in the XP1024/XP128 subsystem-name subwindow. Click the XP Remote Web Console button to start XP Remote Web Console (see section 5-6-5 ). 208
NOTE: The NAS/Management button appears if a NAS-CHA running NAS Manager resides on XP12000/XP10000/SVS200 and XP1024/XP128. Clicking the NAS/Management button opens the Select Nas/Management Port Controller dialog box. Select NAS-CHA, and then click the OK button to launch NAS Manager (see section 5-6-7 ). If you are logged in as a user who has the View permission only, this button does not appear. 2. To edit the storage subsystem properties, click the Modify Properties button in the application bar area to open the Modify Properties window for the storage subsystem (see Figure 10-1).
Figure 10-1 Modifying properties In the Modify Properties window, you can enter the following properties:
Name: Enter a name that identifies the storage subsystem. The name can include
spaces, but cannot consist only of spaces. Leading or trailing spaces are discarded. Enter no more than 60 bytes, using the following characters: A-Z a-z 0-9 - _ . @ / : NOTE: Regarding LUN Scan: If you change the storage subsystem name after a LUN Scan operation, the names of the corresponding logical groups in the LUN SCAN group are not updated. You need to rename those groups to match the new storage subsystem name. If you do not rename the groups, and then execute another LUN Scan on the renamed storage subsystem, a second set of logical groups will be created in the LUN SCAN group using the new storage subsystem name.
User ID (not displayed for XP512/XP48): Enter the user ID that has been set in a storage
subsystem-management tool. Enter no more than 512 bytes.
New Password (not displayed for XP512/XP48): Enter the password that has been set in
a storage subsystem-management tool. Enter no more than 512 bytes. For XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, the user ID is required and the password is optional. 3. When you are finished modifying the properties, click the OK button to modify the properties as specified, or click the Cancel button to cancel your request to modify the properties.
209
10-1-4 Performing a refresh operation

Users with Modify permission who are assigned to the All Resources resource group can perform refresh operations. A refresh operation rediscovers the storage subsystem. You should refresh under the following circumstances:
When changes have made changes to a storage subsystem other than through the Device Manager system (such as adding new disk drives or new XP Business Copy Software pairs using XP RAID Manager or XP Remote Web Console). After the storage subsystem microcode is updated.
CAUTION: Perform a refresh operation after the storage subsystem microcode is updated. CAUTION: After the microcode is updated, the SVP tuning parameters must be set and the SVP must be rebooted before you use Device Manager to refresh the storage subsystem. If you refresh the storage subsystem after the SVP tuning parameters are set, but do not reboot the SVP, the disk unit (DKU) and logical unit number (LUN) information is deleted from the refreshed storage subsystem. CAUTION: You do not need to stop the Device Manager server in order to replace the microcode of a storage subsystem. However, you must ensure that no Device Manager refresh or setup operations (such as adding storage, removing storage, creating logical devices, deleting logical devices, or setting the host mode) are being executed on the corresponding storage subsystem. During microcode replacement, an error may be output to the trace log or error log by polling on the storage subsystem. This error will no longer be output once replacement of the microcode has terminated normally. NOTE: While a storage subsystem is being refreshed, if you shut down the host using a volume of the corresponding storage subsystem or shut down its Device Manager agents, it may take about 15 minutes to complete the refresh operation. NOTE: For the XP24000/XP20000, XP12000/XP10000/SVS200, if you enable the automatic refresh function in the Device Manager server properties, Device Manager executes the refresh operation automatically when the mode is changed from Modify to View. For details about how to set the properties file, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. NOTE: If you are using XP12000/XP10000/SVS200 XP External Storage Software, each time you add an external subsystem after adding XP12000/XP10000/SVS200, you must refresh the XP12000/XP10000/SVS200 subsystem. If you add an external subsystem to Device Manager after you have added a storage subsystem that uses XP External Storage Software, you must perform a refresh operation on the storage subsystem. To perform a refresh operation: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the application bar area, click the Refresh button. The Refresh Storage Subsystem-Confirmation window appears. 3. To refresh the storage subsystem information, click the OK button. To cancel the request to refresh the storage subsystem information, click the Cancel button. You are notified when the refresh operation is complete.
10-1-5 Adding a new IP address

When the IP address of a storage subsystem is changed, a user with Modify permission who is assigned to the All Resources resource group must re-register that storage subsystem. 210
Performing storage subsystem operations To re-register a storage subsystem subsystem when a new IP address has been added: 1. Back up the databases on the Device Manager server. For details on database backup, see HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. 2. Add the storage subsystem with the changed IP address to Device Manager, making sure to enter the new IP address in the Add Subsystem window (see section 10-1-2 for instructions). 3. After the storage subsystem discovery process is complete, check the storage subsystem properties to verify that the new IP address is displayed. NOTE: When you change the IP address of the storage subsystem, even if you re-register the storage subsystem using the new IP address, the following information will not be updated: Storage subsystem name used in web client. To change the storage subsystem name, enter the new name on the Modify Properties window (see section 10-1-3 for instructions). Name of the logical group in LUN Scan. To change the name of the logical group in the LUN SCAN group, enter the new name on the Modify Properties window for the logical group (see section 7-4 for
instructions).
10-1-6 Removing a storage subsystem

Users with Modify permission who are who are assigned to the All Resources resource group can remove a storage subsystem from Device Manager. When you remove a storage subsystem, all related volumes, components, and storage groups are removed from Device Manager, however, the removal operation does not affect the storage subsystem itself. NOTE: If you remove a storage subsystem that has alert information, and then attempt to display the alert information for the removed subsystem, ARRAY.storage -subsystem-type (such as ARRAY.XP10000) is displayed as the source. In this case, either delete the alert information if it is not needed, or add the storage subsystem to Device Manager again.
To remove a storage subsystem from the Device Manager: 1. In the Explorer menu, select Resources and then Subsystems and then select a storage subsystem in the navigation area. 2. In the application bar area, click the Remove Subsystem button. The Remove Subsystem-Confirmation window appears. 3. To remove the storage subsystem, click the OK button. To cancel the request to remove the storage subsystem, click the Cancel button. After processing finishes, a message reports that the storage subsystem delete operation is completed. 4. If the storage subsystem is associated with any logical groups, Device Manager displays an important warning. After reading the warning, select YES to go ahead and remove the storage subsystem, or select NO to cancel your request. You are notified when the remove storage subsystem operation is complete.
10-2 Viewing detailed information and changing configuration of the storage subsystem
Users who are assigned the All Resources resource group can view detailed information and change configuration of the storage subsystem. You can view detailed information and change configuration of the storage subsystem in the Physical View dialog box of each storage subsystem. 211
NOTE: To display Physical View for XP24000/XP20000 or XP12000/XP10000/SVS200, XP Remote Web Console must be installed on the storage subsystem that is to be managed by Device Manager. From the Physical View of each storage subsystem, you can launch a web application specified using the URLLink feature. This section describes viewing detailed information and changing the configuration of each storage subsystem as follows:
Viewing and configuring information for XP24000/XP20000 (see section 10-2-1 ) Viewing and configuring information for XP12000/XP10000/SVS200 (see section 10-2-2 ) Viewing information for XP1024/XP128 (see section 10-2-3 ) Viewing information for XP512/XP48 (see section 10-2-4 ) Viewing LDEV information (see section 10-2-5 )
Size information in the Physical View The total size that is displayed is not the total size of the physical disk. It is the total available disk size, which means the total of the sizes of all logical devices on the machine. Thus, this total size is increased or decreased by creating or deleting logical devices.
10-2-1 Viewing information for XP24000/XP20000

Users assigned the All Resources resource group can use the Physical View for XP24000/XP20000. Available operations depend on the permission set for the user. The following describes available operations for each permission:
Users with the Modify permission can set the configuration of XP24000/XP20000. Users with the View permission can view detailed information of XP24000/XP20000.
NOTE: In XP24000/XP20000, if you enable the automatic refresh function in the Device Manager server properties, Device Manager automatically performs a refresh operation when the mode is changed from Modify to View in the Physical View for XP24000/XP20000. For details about how to set the properties file, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. NOTE: If SSL is set on XP Remote Web Console, a warning dialog box for security might appear. After the certificate has been imported to the browser, this dialog box is no longer displayed. To view detailed information for XP24000/XP20000: 1. In the Explorer menu, select Resources and then Subsystems, and then select the desired XP24000/XP20000 in the navigation area. The subsystem-name subwindow appears in the application area. 2. In the subsystem-name subwindow, click the Physical View button to open the Physical View for the selected XP24000/XP20000. XP Remote Web Console starts as the Physical View for XP24000/XP20000. In the Physical View, you can view and configure the detailed information about XP24000/XP20000. For details, refer to the HP StorageWorks XP Remote Web Console user guide.
10-2-2 Viewing information for XP12000/XP10000/SVS200

Users assigned to the All Resources resource group can use the Physical View for XP12000/XP10000/SVS200. Available operations depend on the permission set for the user. The following describes available operations for each permission:
Users with Modify permission can set the configuration of XP12000/XP10000/SVS200. 212
Users with View permission can view detailed information of XP12000/XP10000/SVS200.
IMPORTANT: To display Physical View for XP12000/XP10000/SVS200, the Java heap size for XP Remote Web Console must be set to 256 MB. For details on how to set the Java heap size for XP Remote Web Console, see the XP Remote Web Console manual. NOTE: In XP12000/XP10000/SVS200, if you enable the automatic refresh function in the Device Manager server properties, Device Manager automatically performs a refresh operation when the mode is changed from Modify to View in the Physical View for XP12000/XP10000/SVS200. For details about how to set the properties file, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. NOTE: If SSL is set on XP Remote Web Console, a warning dialog box for security might appear. After the certificate has been imported to the browser, this dialog box is no longer displayed. To view detailed information about XP12000/XP10000/SVS200 in the Physical View: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired XP12000/XP10000/SVS200 subsystem in the navigation area. The subsystem-name subwindow appears in the application area. 2. In the subsystem-name subwindow, click the Physical View button to open the Physical View for the selected XP12000/XP10000/SVS200. XP Remote Web Console starts in the Physical View for XP12000/XP10000/SVS200. In the Physical View, you can view and configure the detailed information about XP12000/XP10000/SVS200. For details, refer to the HP StorageWorks XP Remote Web Console user guide.

Users assigned to the All Resources resource group can perform Physical View operations. To view detailed information for an XP1024/XP128 storage subsystem: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired XP1024/XP128 storage subsystem. The subsystem-name subwindow appears in the application area. 2. In the subsystem-name subwindow, click the Physical View button to open the Physical View for the selected XP1024/XP128 storage subsystem (see Figure 10-2). The CONFIGURATION button is selected in the initial window, which displays the storage subsystem properties, such as serial number, IP address, microcode, and capacity. 3. In the Physical View area, you can select the desired port to open the Port Information window. For example, to view the information for the CL1 E port, select the E button inside the Cluster 1 frame. For details on the Port Information window, see section 10-3 . 4. In the Physical View area, selecting the PORT CONTROLLERS button opens the Port Controller window. For details on the Port Controller window, see section 10-3-4 . 5. To view array group information, click the ARRAY GROUPS button (see Figure 10-3). 6. In the array groups view, you can click the VIEW button for the desired frame to open the Frame Information (level 1) window (see Figure 10-4). IMPORTANT: The XP1024/XP128 has the capability to integrate two array groups and handle them as a single array group. This is called a discrete VDEV configuration (see Figure 10-5). A discrete VDEV configuration logically integrates two sets of 2D+2D (RAID1) into a single set of 2D+2D (RAID1) by integrating two array groups. For a discrete VDEV configuration, Coupled is displayed in the parity group list along with the remote parity group (Coupled:1-2). If you select a parity group of a discrete VDEV configuration in the Frame Information (level 1) window, Frame Information (level 2) window
213
Performing storage subsystem operations displays information only for array groups belonging to the representative VDEV. No information is displayed for array groups that do not belong to the representative VDEV. For a discrete VDEV configuration, the Frame Information window displays the information shown in Figure 10-6. NOTE: For a 7D+1P array group, Coupled displays next to the parity group number (Parity Group 1-2(Coupled:2-2)). In this case, information about the parity group indicated by Coupled (example: 2-2) is not displayed (see Figure 10-4). 7. In the Frame Information (level 1) window, you can select the desired array group to open the Frame Information (level 2) window (see Figure 10-7). 8. In the Frame Information (level 2) window, you can select the desired array group to open the LDEV Information window. For details on this window, see section 10-2-5 . 9. To view the disk information, click the DISKS button in Physical View (see Figure 10-8).
Figure 10-2 Physical View for XP1024/XP128 (Configuration) The XP1024/XP128 Physical View (Configuration) window displays the following information and buttons:
Model: The type (vendor model) of the storage subsystem, such as XP128 Serial: The (vendor) serial number of the storage subsystem IP Address: The IP address of the storage subsystem Microcode SVP: The microcode level of the service processor Microcode DKC: The microcode level of the disk controller Configured Capacity: The configured capacity of the storage subsystem (the total capacity of all LDEVs, not the total capacity of the physical disks). The Configured Capacity increases or decreases when logical devices are created or deleted. Total Cache: The total cache capacity of the storage subsystem PORT CONTROLLERS button: Opens the Port Controller window (see section 10-3-4 ) Port buttons (such as E under Cluster 1 for port CL1 E): Open the Port Information window for the selected port (see section 10-3 )
214
NOTE: The following ports are not displayed: CL1-S, CL1-T, CL1-U, CL1-V, CL1-W, CL1-X, CL1Y, CL1-Z, CL2-S, CL2-T, CL2-U, CL2-V, CL2-W, CL2-X, CL2-Y, CL2-Z. NOTE: If you use disk units of XP512/XP48 for XP1024/XP128, the Physical View displays six disk units (three units on each side) in total in the maximum configuration.
Figure 10-3 Physical View for XP1024/XP128 (Array Groups) When you click the ARRAY GROUPS button the XP1024/XP128 Physical View (Array Groups) window displays the following information and buttons:
In the Array Groups area: Displays the number of array groups and capacity for each array control processor (ACP) and the total number of array groups and total capacity for all ACPs. The displayed capacity of the array group is truncated to two decimal places. This may cause the total capacity of the array group to be less than the sum of the capacity of the array groups. However, this does not mean that the actual available capacity has been reduced.
The VIEW button: Opens the Frame Information (level 1) window for the selected frame (see Figure 10-4). The PORT CONTROLLERS button: Opens the Port Controller window (see section 10-3-4 ). The lettered Port buttons in Cluster graphic (such as E under Cluster 1 for port CL1 E): Open the Port Information window for the selected port (see section 10-3 ). The following ports are not displayed: CL1-S, CL1-T, CL1-U, CL1-V, CL1-W, CL1-X, CL1-Y, CL1-Z, CL2-S, CL2-T, CL2-U, CL2-V, CL2-W, CL2-X, CL2-Y, CL2-Z
NOTE: If you use disk units of XP512/XP48 for XP1024/XP128, virtual devices and parity groups appear to be in a one-to-one relationship. For example, if you use disk units of XP512/XP48 in six frames of XP1024/XP128, 1 to 12 parity groups (blue icons) are displayed.
215
Figure 10-4 Frame Information window for XP1024/XP128 (Level 1) The XP1024/XP128 Frame Information (level 1) window displays the storage subsystem name, ACP number, frame number, and list of parity groups (maximum 32) for the frame that you selected when in the Array Group view using the VIEW button in the Physical View. The XP1024/XP128 has a maximum of 512 array groups on one chassis (the parts displayed in pair both at the top and bottom of the frame). The Frame Information (level 1) window displays from 1 to 32 parity groups, each of which can have a maximum of 16 array groups. Selecting a parity group opens the Frame Information (level 2) window (see Figure 10-7). NOTE: If you use disk units of XP512/XP48 for XP1024/XP128, the Frame Information (level 1) window displays from 1 to 12 parity groups in line. Because the actual device has only one virtual device in one parity group, the Frame Information (level 2) window always displays only one array group.
216
Figure 10-5 Discrete VDEV configuration for XP1024/XP128
217
Figure 10-6 Frame Information window for discrete VDEV configuration
218
Figure 10-7 Frame Information window for XP1024/XP128 (Level 2) The Frame Information (level 2) window displays the storage subsystem name, ACP number, frame number, and list of array groups (16 maximum) for the parity group that you selected in the Frame Information (level 1) window. The following information is displayed in the Frame Information (Level 2) window for each array group:
Array group ID Number of disks in the array group and their capacity (4 x 72 GB: Four 72-GB disk drives) Capacity of the array group
Selecting an array group opens the LDEV Information window (see section 10-2-5 ). NOTE: If you use disk units of XP512/XP48 for XP1024/XP128, the Frame Information (level 1) window displays from 1 to 12 parity groups in line. Because the actual device has only one virtual device in one parity group, the Frame Information (level 2) window always displays only one array group.
219
Figure 10-8 Physical View for XP1024/XP128 (Disks) The Disks view of the XP1024/XP128 Physical View displays the following information and buttons:
ACP: Displays the number of disks and capacity for each array control processor and the total number of disks and total capacity for all ACPs PORT CONTROLLERS button: Opens the Port Controller window (see section 10-3-4 ) Port buttons (such as E under Cluster 1 for port CL1 E): Open the Port Information window for the selected port (see section 10-3 ). The following ports are not displayed: CL1-S, CL1-T, CL1-U, CL1-V, CL1-W, CL1-X, CL1-Y, CL1-Z, CL2-S, CL2-T, CL2-U, CL2-V, CL2-W, CL2-X, CL2-Y, CL2-Z.
NOTE: If you use disk units of XP512/XP48 for XP1024/XP128, in the same way as when you use disk units of XP1024/XP128, the number of installed disks and the total number of installable disks are displayed for each chassis.

Users assigned to the All Resources resource group can perform Physical View operations for XP512/XP48. To view detailed information for an XP512/XP48 storage subsystem: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired XP512/XP48 storage subsystem. The subsystem-name subwindow appears in the application area. 2. In the subsystem-name subwindow, click the Physical View button to open the Physical View for the selected XP512/XP48 storage subsystem (see Figure 10-9). The CONFIGURATION button is selected in the initial window, which displays the storage subsystem properties, such as serial number, IP address, microcode, and capacity. 3. In the Physical View, you can select the desired port to open the Port Information window. For example, to view the information for the CL1 E port, click the E button inside the Cluster 1 frame. For details on the Port Information window, see section 10-3 . 4. In the Physical View, you can click the PORT CONTROLLERS button to open the Port Controller window. For details on the Port Controller window, see section 10-3-4 . 220
Performing storage subsystem operations 5. To view array group information, click the ARRAY GROUPS button (see Figure 10-10). 6. In the array groups view, you can click the VIEW button for the desired frame to open the Frame Information window (see Figure 10-11). 7. In the Frame Information window, you can select the desired array group to open the LDEV Information window. For details on the LDEV Information window, see section 10-2-5 . 8. In the Physical View, click the DISKS FRONT or DISKS BACK button (DISKS button for XP48) to view the disk information (see Figure 10-12).
Figure 10-9 Physical View for XP512/XP48 (Configuration) The XP512/XP48 Physical View (Configuration) displays the following information and buttons:
Model: The vendor model of the storage subsystem, such as XP512 Serial: The (vendor) serial number of the storage subsystem IP Address: The IP address of the storage subsystem Microcode SVP: The microcode level of the service processor Microcode DKC: The microcode level of the disk controller Configured Capacity: The configured capacity of the storage subsystem (the total capacity of all LDEVs, not the total capacity of the physical disks). The Configured Capacity increases or decreases when logical devices are created or deleted. Total Cache: The total cache capacity of the storage subsystem PORT CONTROLLERS button: Opens the Port Controller window (see section 10-3-4 ) Port buttons (such as E under Cluster 1 for port CL1 E): Open the Port Information window for the selected port (see section 10-3 )
221
Figure 10-10 Physical View for XP512/XP48 (Array Groups) The XP512/XP48 Physical View (Array Groups) displays the following information and buttons:
Array Groups: Displays the number of array groups and capacity for each array control processor (ACP) and the total number of array groups and total capacity for all ACPs.
NOTE: For the XP512/XP48 storage subsystem, 0 GB is determined as the capacity of an array group for which a mainframe emulation type (such as 3390-3) is set. NOTE: The displayed capacity of the array group is truncated to two decimal places. This may cause the total capacity of the array group to be less than the sum of the capacity of the array groups. However, this does not mean that the actual available capacity has been reduced.
VIEW button: Opens the Frame Information window for the selected frame (see Figure 10-4). PORT CONTROLLERS button: Opens the Port Controller window (see section 10-3-4 ). Port buttons (such as E under Cluster 1 for port CL1 E): Open the Port Information window for the selected port (see section 10-3 ).
222
Figure 10-11 Frame Information window for XP512/XP48 The Frame Information window displays the storage subsystem name, ACP number, frame number, and list of array groups for the selected frame. The following information is displayed for each array group:
Array group ID Number of disks in the array group and their capacity (4 x 72 GB: Four 72-GB disk drives) Capacity of the array group
Selecting an array group opens the LDEV Information window (see section 10-2-5 ).
223
Figure 10-12 Physical View for XP512/XP48 (Disks) The Disks view of the XP512/XP48 Physical View displays the following information and buttons:
ACP: Displays the number of disks and capacity for each array control processor and the total number of disks and total capacity for all ACPs. PORT CONTROLLERS button: Opens the Port Controller window (see section 10-3-4 ). Port buttons (such as E under Cluster 1 for port CL1 E): Open the Port Information window for the selected port (see section 10-3 ).
10-2-5 Viewing LDEV information

Users assigned to the All Resources resource group can view the detailed LDEV information. NOTE: After you have performed an operation on the LDEV Information window, the contents of the LDEV Information window are updated. However, the LDEV list may display only some of the LDEVs. In this case, close the LDEV Information window, and then open it again to display all LDEVs.
To view the detailed LDEV information: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. The subsystem-name subwindow appears in the application area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem, and then open the LDEV Information window as follows:
For XP1024/XP128: Click the VIEW button for the desired frame. Select the desired parity group on the Frame Information (level 1) window. For XP1024/XP128, click the VIEW button for the desired frame on the ARRAY
GROUPS view, select the desired parity group on the Frame Information (level 1) window, and then select the desired array group on the Frame Information (level 2) window.
224
For XP512/XP48, click the VIEW button for the desired frame on the ARRAY GROUPS
view, select the desired array group on the Frame Information window.
Select the desired array group. For XP512/XP48: Click the VIEW button for the desired frame. Select the desired array group on the Frame Information window. Select the desired array group.
3. The LDEV Information window consists of the following three display areas:
LDEV List (upper left):

Displays a list of logical devices in the selected array group. Select the desired LDEV in this list to display the detailed LDEV information. Each LDEV row displays the following information:
The LDEV number and size (MB, fractional portion truncated) If a path has been set, the port is also displayed. If the LDEV is part of a LUSE volume, the following information is displayed: (LUSE:
representative-logical-device-number).
For XP1024/XP128 and XP512/X48, the capacity of an HRX intermediate volume is

also displayed (capacity in MB and Cyl). For more information on the HRX intermediate volume, refer to the documentation for the storage subsystem that you use.
Array Group Info (upper right):

Displays the detailed information for the selected array group:
ACP (XP1024/XP128 only) Array group name, disk size, RAID level, emulation type (XP1024/XP128 and
XP512/XP48 only)
Free space, largest space (largest amount of contiguous free space in the array group). LDEV information (lower part). Displays the detailed information for the selected LDEV.
Provides the following tabs (see below for descriptions of these tabs):
Detail tab Path Info tab Pair Info tab

The LDEV Information window provides the following buttons:
ALLOCATE: Enables you to allocate a path to the selected logical device. UNALLOCATE: Enables you to release the path that is allocated to the selected LDEV.
Select the check box of the desired path on the Path Info tab to activate this button.
CREATE LDEV: Enables you to create logical devices in an array group. DELETE LDEV: Enables you to delete the selected logical device from the array group.
Select a logical device to which no path is set to activate this button.
LDEV CONFIG: Enables you to set a command device. Selecting a logical device that
can be set as a command device activates the LDEV CONFIG button. The Detail tab of the LDEV Information window displays the following information. You can sort the displayed information by selecting the desired column heading.
LDEV: LDEV number. For a LUSE volume, you can display the information for a logical device by selecting its number from the drop-down list of the logical devices in the LUSE volume. Capacity: Capacity of the logical devices. For a LUSE volume, displays the capacity of the LUSE volume rather than of the capacity of individual logical devices. For XP1024/XP128 and XP512/XP48, also displays the capacity of the HRX intermediate volume. 225
Performing storage subsystem operations The capacity values are in megabytes with the fractional portions dropped. The displayed value may, therefore, be less than the actual available capacity. For an HRX intermediate volume, the capacity in cylinders (number-of-cylinders Cyl) is displayed alongside the capacity in megabytes. For more information on the HRX intermediate volume, refer to the documentation for your the storage subsystem.
EMU Type: Emulation type for XP1024/XP128 or XP512/XP48 only, for example, OPEN-x Copy Type:
BC (XP Business Copy Software) Cnt Ac-S (XP Continuous Access Synchronous Software) Cnt Ac-A (XP Continuous Access Asynchronous Software) Cnt Ac (XP Continuous Access Software whose synchronization mode is unknown) Snapshot (XP Snapshot) Unpaired none (pair status unknown)
NOTE: Cnt Ac is displayed when the subsystem containing the primary volume is not registered with Device Manager. However, if the subsystem containing the secondary volume is an XP1024/XP128, the synchronization mode information is available as Cnt Ac-S or Cnt Ac-A.
Volume Attr: Provides the following options:
CVS (custom-sized volume created by using XP Virtual LVI/LUN (VLL) and Volume
Shredder)
LUSE LUSE (CVS) (LUSE volume made up of CVS volumes) POOL (data pool) GUARD (XP Data Retention Utility is set up) External (external volume) OnDemand (on-demand volume) Migration-reserved (reserve volume used in XP Auto LUN Software) none (normal volume)
CMD DEV: CMD DEV, Remote, or none (not a command device nor a remote command device) Guard Mode(Attribute): Attribute of the logical device (XP1024/XP128 only)) Guard Mode(S-VOL): S-VOL Disable attribute (XP1024/XP128 only) Guard Mode(Mode): The INH bit attribute (XP1024/XP128 only)
The Path Info tab of the LDEV Information window displays the following information. You can sort the displayed information by selecting the desired column heading.
LDEV: LDEV number. For a LUSE volume, displays only the representative LDEV number. To select the path of the logical device to be unallocated, select the check box of the path. Port/HSD/LUN or Port/LUN:
Displays port, host storage domain, and logical unit number for XP1024/XP128. Displays the port and logical unit number for XP512/XP48.
Group: Name of the storage group to which the volume path belongs Host: Host name and WWN Filesystem: Mount point on the host (displayed only when a Device Manager agent is installed on the host)
226
Host Bus/TID/LUN: SCSI information that the host recognizes (displayed only when a Device Manager agent is installed on the host) Capacity: Capacity of the LDEV. For XP1024/XP128 and XP512/XP48, this item also displays the capacity of an HRX intermediate volume. The displayed values are in megabytes (MB) with the fractional portions dropped. Therefore, the displayed value may be less than the actual available capacity. For an HRX intermediate volume, the capacity in cylinders (number-of-cylinders Cyl) is displayed alongside the capacity in megabytes. For more information on the HRX intermediate volume, refer to the documentation for the your storage subsystem.
% Used: Percentage of volume usage (displayed only when a Device Manager agent is installed on the host), see section 8-2-1 . When multiple paths are assigned to a volume, the following information is displayed:
When a path is assigned to multiple hosts

The percentage of volume usage on a host to which the Device Manager agent last sent the data is displayed. If the percentage of volume usage cannot be calculated on that host, even if the volume is being used by another host, two dashes (--) are displayed.
When multiple paths are assigned to a single host

The largest value is displayed as the percentage of storage usage. For details about how to calculate the percentage of volume usage and details about the conditions that prevent this item from being displayed, see the description of %Used in section 8-2-1 .
Last Updated: Time of the last update performed by the Device Manager agent (only when a Device Manager agent is installed on the host). If multiple paths are assigned to the volume, the date and time when information was last updated on a host to which Device Manager agent last sent the data is displayed.
The items displayed in the Pair Info tab of the LDEV Information window depend on the volume attribute. When the volume attribute is other than POOL, copy pair information is displayed. For a POOL volume, the POOL ID is displayed as the POOL information. You can sort the information by selecting the desired column heading. The following display items appear in Pair Info tab of the LDEV Information window for volume attributes other than POOL:
Copy Type:
BC (XP Business Copy Software) Cnt Ac-S (XP Continuous Access Synchronous Software) Cnt Ac-A (XP Continuous Access Asynchronous Software) Cnt Ac (XP Continuous Access Software whose synchronization mode is unknown) Snapshot (XP Snapshot) Unpaired none (pair status unknown)
NOTE: Cnt Ac is displayed when the storage subsystem containing the primary volume is not registered with Device Manager. However, if the storage subsystem containing the secondary volume is an XP1024/XP128, the synchronization mode information is available. When Cnt Ac is displayed, copy information is not available, and Copy Status displays no value.
Copy Status:
Simplex (SMPL) Pair (PAIR) Copying (COPY(PD), COPY(RS), COPY(SP), or COPY)

227
Reverse-Copying (COPY(RS-R) Split (PSUS or PSUS(SP)) Suspended (PSUE) Error in LUSE (PDUB) Suspending (Suspending) Deleting (Deleting) none displayed (copy status is unknown)
Fence Level: Setting for recovery performed when a failure occurs in execution of XP Continuous Access Software. For details, refer to the applicable XP Continuous Access Software manual. LDEV(P-VOL): Logical device number of the primary volume Type(P-VOL): Model name of the storage subsystem to which the primary volume belongs. Displays Unknown if the storage subsystem to which the primary volume belongs is not discovered. Serial No.(P-VOL): Serial number of the storage subsystem to which the primary volume belongs. For XP512/XP48, displays Unknown if the storage subsystem to which the primary volume belongs is not discovered. AG(P-VOL): Number of the array group to which the P-VOL belongs LDEV(S-VOL): Logical device number of the S-VOL Type(S-VOL): Model name of the storage subsystem to which the secondary volume belongs. Displays Unknown if the storage subsystem to which the secondary volume belongs is not discovered. Serial No.(S-VOL): Serial number of the storage subsystem to which the secondary volume belongs AG(S-VOL): Number of the array group to which the S-VOL belongs
NOTE: To display or update XP Business Copy Software and XP Continuous Access Software settings for XP1024/XP128, you must refresh the storage subsystem information: For details on the system configuration required to display the XP Business Copy Software and XP Continuous Access Software settings of storage subsystems, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide
10-3 Port operations

Device Manager port operations include:
Configuring ports (XP1024/XP128 and XP512/XP48) (see section 10-3-1 ) Managing LUN groups (see section 10-3-2 ) Managing WWN groups (see section 10-3-3 ) Configuring Fibre Channel adapters (XP1024/XP128 and XP512/XP48) (see section 10-3-4 )
NOTE: For the iSCSI ports (XP1024/XP128), NAS-CHA ports (XP1024/XP128), and mainframe ports (XP1024/XP128 or XP512/XP48), you can reference the port configuration but you cannot change it. NOTE: To perform an operation on a port for XP24000/XP20000, use the Physical View for XP24000/XP20000 (see section 10-2-1 ). NOTE: To perform an operation on a port for XP12000/XP10000/SVS200, use the Physical View for XP12000/XP10000/SVS200 (see section 10-2-2 ).
228
10-3-1 Configuring ports (XP1024/XP128 and XP512/XP48)

Users with Modify permission who are assigned to the All Resources resource group can configure Fibre Channel ports on the XP1024/XP128 and XP512/XP48 subsystems. Table 10-1 lists available arbitrated loop-port address (AL-PA) values ranging from 01 to EF. Table 10-1 Available AL-PA values Values
EF CD B2 E8 CC B1 98 97 72 71 6E 6D 6C 55 54 53 52 51 3A 39 36 35 34 33 32 31 25 23 1F 1E 1D 1B 18 17 10
E4 CB AE 90 E2 CA AD 8F E1 E0 C9 AC 88 C7 AB 84
6B 4E 6A 4D 69 67 66 65 63 5C 5A 59 56 4C
DC C6 AA 82 DA C5 A9 D9 C3 A7 81 80
4B 2E
D6 BC A6 7C D5 BA A5 7A D4 D3 D2 D1 B9 A3 B6 9F 79 76 75 74 73
4A 2D 0F 49 47 46 45 43 3C 2C 2B 2A 29 27 26 08 04 02 01
B5 9E B4 9D
CE B3 9B
To configure the ports: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display Physical View for the storage subsystem. 3. In the Physical View, select the desired port to open its Port Information window (see Figure 10-13). NOTE: For XP1024/XP128, the following ports are not displayed in the Physical View: CL1-S, CL1-T, CL1-U, CL1-V, CL1-W, CL1-X, CL1-Y, CL1-Z, CL2-S, CL2-T, CL2-U, CL2-V, CL2-W, CL2X, CL2-Y, CL2-Z. 4. On the Port Information window, change the port settings as desired. For details on the port information and settings for each storage subsystem, see the descriptions below. NOTE: If you change the Topology (Connection) settings, the attributes displayed by web client wait for ten seconds after changing the setting to allow the change to take effect in the storage subsystem, and then refresh the storage subsystem (see section 10-1-4 ). The updated Topology (Connection) value should appear.
229
NOTE: If you changed the Fibre Addr setting, if the new setting does not take effect immediately make sure that the specified port is connected to a fibre network, and then refresh the storage subsystem information (see section 10-1-4 ). 5. After making the desired changes to the port settings, click the OK button to change the port settings as specified, or click the Cancel button to cancel your request to change the settings. 6. When the Confirmation window is displayed, review the requested operations, and select YES to change the port settings, or select NO to cancel your request. A system message notifies you are notified when the port change operation is complete. CAUTION: If you change the attributes of a port, the host currently accessing the port may no longer be able to access the storage. Before changing the settings, you must stop all I/O operations with the host. If you use Device Manager to change the port settings while I/O operations between the host and the storage subsystem are underway, the I/O operations may terminate abnormally.
Figure 10-13 Port Information window for the XP1024/XP128 Settings for the Port Information window for the XP1024/XP128 Series:
Port name: Ports with lower-case characters are activated for XP1024/XP128 with a 16-port channel adapter.
For a port with lower-case characters that exists in a channel adapter on cluster 1, CL3-x
is displayed as the port name.
For a port with lower-case characters that exists in a channel adapter on cluster 2, CL4-x
is displayed as the port name.
Port settings:
230
LUN Security: Enable or disable LUN security for all LUNs on the port. To secure LUNs,
select Enabled. If no LUN security at all is desired, you can select Disabled.
Topology (Fabric): Select On, Off Topology (Connection): Select FC-AL, Point-to-Point Fibre Addr: In fabric environments, the port address is assigned automatically by fabric switch port
number and is not controlled by the XP1024/XP128 port settings.
In arbitrated loop environments, select an AL-PA (or loop ID) value to be set for the port
address from the drop-down list. See Table 10-1 for the available AL-PA values.
Channel Speed: Select 1 GB/s, 2 GB/S, or auto (cannot be modified for some port types)
Host storage domain settings:
Host Storage Domain Name: The host storage domain name is displayed. You can
change the HSD name, which can be a maximum of eight characters using only the following characters: A-Z a-z 0-9 ! # $ % & ' ( ) + - . = @ [ ] ^ _ ` { } ~ The host storage domain name can include spaces, but cannot consist only of spaces. Leading or trailing spaces are discarded.
Host Mode: Solaris, HP, AIX, Windows, NetWare, etc. (Selectable host modes vary
depending on the microcode version). Select for the connected platform to enable the host to "see" all LUNs on the port. If Device Manager cannot recognize the host mode specified for the host storage domain. Unknown is displayed. For more information on the host mode, see the LAN Management manual for XP1024/XP128.
LUN Security: Host name/WWN for each WWN in the selected host storage domain WWN Info button: Displays the WWN(s) registered to the port
The port Information window for XP512/XP48:
LUN Security: Enable or disable LUN security for all LUNs on the port. To secure LUNs, select Enabled. If no LUN security at all is desired, select Disabled. Topology (Fabric): Select On, Off Topology (Connection): Select FC-AL, Point-to-point Fibre address.
In fabric environments, the port address is assigned automatically by fabric switch port
number and is not controlled by the XP512/XP48 port settings.
In arbitrated loop environments, select an AL-PA (or loop ID) value to be set for the port
address from the drop-down list. see Table 10-1 for the available AL-PA values.
Host Mode: Solaris, HP, AIX, Windows, NetWare, etc. Select the host mode for the connected platform to enable the host to "see" all LUNs on the port. For details on the host mode, see the LAN Manager manual for XP512/XP48. If Device Manager cannot recognize the host mode that is specified for the port, Unknown is displayed. Modify LUN Group: Opens the Modify LUN Group window (see section 10-3-2 ). Modify WWN Group: Opens the Modify WWN Group window (see section 10-3-3 ). WWN Info button: Displays the WWN(s) registered to the port and the WWN Group to which each WWN belongs (if any).
10-3-2 Managing LUN groups

Users with Modify permission who are assigned to the All Resources resource group can manage LUN groups on XP512/XP48.
231
Performing storage subsystem operations The Modify LUN Group window (see Figure 10-14) enables you to create, modify, and delete LUN groups for each XP512/XP48 port. To open the Modify LUN Group window, open the Port Information window for the desired port (see section 10-3-1 ), and click the MODIFY LUN GROUP button.
Figure 10-14 Modify LUN Group window The Select LUN Group drop-down list box enables you to select the desired LUN group. The DELETE THIS GROUP button enables you to delete the selected LUN group. The CREATE NEW GROUP button enables you to create a new LUN group to the selected port. The SAVE button saves your changes on this window and returns you to the Port Information window.
LUN tab:
The Ungrouped list box displays the LUN(s) that can be added to the selected LUN
group.
The Grouped list box displays the LUN(s) in the selected LUN group. The ADD>> button moves the selected LUN(s) to the Grouped list. The << REMOVE button moves the selected LUN(s) to the Ungrouped list.
WWN tab:
The Unsecured list box displays the WWN(s) that can be added to the selected LUN
group.
The Secured list box displays the WWN(s) in the selected LUN group. The ADD>> button moves the selected WWN(s) to the Secured list. The << REMOVE button moves the selected WWN(s) to the Unsecured list.
WWN Group tab:
The Unsecured list displays the WWN group(s) that can be added to the selected LUN
group.
The Secured list box displays the WWN group(s) in the selected LUN group.
232
The ADD>> button moves the selected WWN group(s) to the Secured list. The << REMOVE button moves the selected WWN group(s) to the Unsecured list.
10-3-2-1 Creating a LUN group

To create a new LUN group: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. In Physical View, select the desired port (for XP512/XP48 port CL1-A, click A in Cluster 1) to open the Port Information window. 4. Click the MODIFY LUN GROUP button to open the Modify LUN Group window (see Figure 10-14). 5. Select CREATE NEW GROUP, enter the desired name for the new LUN group, and click the OK button. The name must be no more than 8 bytes in length. You can use only the following characters for the name: A-Z a-z 0-9 ! # $ % & ' ( ) + - . = @ [ ] ^ _ ` { } ~ LUN group names are case-sensitive and must be unique. 6. Click the LUN tab of the Modify LUN Group window, add the desired LUN(s) to the new LUN group: select the desired LUN(s) in the Ungrouped list, and select ADD>> to move the selected LUN(s) to the Grouped list. If necessary, use the << REMOVE button to move LUN(s) back into the Ungrouped list. 7. Click the WWN tab of the Modify LUN Group window, to add the desired WWN(s) to the new LUN group: select the desired host WWN(s) in the Unsecured list, and select ADD>> to move the selected WWN(s) to the Secured list (see Figure 10-15). If necessary, use the << REMOVE button to move WWN(s) back into the Unsecured list.
Figure 10-15 Creating a new LUN GroupSelecting the WWN(s)
233
Performing storage subsystem operations 8. Click the WWN Group tab of the Modify LUN Group window, add the desired WWN group(s) to the new LUN group: select the desired WWN group(s) in the Unsecured list, and select ADD>> to move the selected WWN group(s) to the Secured list (see Figure 10-16). If necessary, use << REMOVE to move WWN group(s) back into the Unsecured list.
Figure 10-16 Creating a new LUN GroupSelecting the WWN Group(s) 9. When you have added all desired LUN(s), WWN(s), and WWN group(s) to the new LUN group, click the SAVE button, or click the CANCEL button to cancel your request. 10. When the confirmation window is displayed, select YES to add the new LUN group, or select NO to cancel your request.
10-3-2-2 Modifying a LUN group

To modify an existing LUN group: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. In the Physical View, select the desired port (for XP512/XP48 port CL1-A, then click A in Cluster 1) to open the Port Information window. 4. Click the MODIFY LUN GROUP button to open the Modify LUN Group window (see Figure 10-14). 5. Select the desired LUN group, and make the desired changes to the LUN group.
To add/ remove LUN(s), click the LUN tab. To add/ remove WWN(s), click the WWN tab. To add/ remove WWN group(s), click the WWN Group tab. To change the name of a LUN group, enter the new name in the Select LUN Group field.
6. When the Modify LUN Group window id displayed the desired changes for the selected LUN group, click the SAVE button to modify the LUN group, or click the CANCEL button to cancel your.
234
Performing storage subsystem operations 7. When the confirmation window is displayed, select YES to modify the LUN group, or select NO to cancel your request.
10-3-2-3 Deleting a LUN group

To delete a LUN group: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. In the Physical View, select the desired port (for XP512/XP48 port CL1-A, click A in Cluster 1) to open the Port Information window (see Figure 10-13). 4. Click the MODIFY LUN GROUP button to open the Modify LUN Group window (see Figure 10-14). 5. Select the desired LUN group, then click the DELETE THIS GROUP button, and select YES on the confirmation window, or select NO to cancel your request to delete the LUN group. If you selected YES, the LUN group to be deleted is no longer displayed on the Modify LUN Group window. 6. Click the SAVE button on the Modify LUN Group window to delete the LUN group(s), or click the CANCEL button to cancel your request to delete the LUN group(s). 7. When the confirmation window is displayed, click the YES button to delete the LUN group. Click the NO, and then click the CANCEL button on the Modify LUN Group window.
10-3-3 Managing WWN groups

Users with Modify permission who are assigned to the All Resources resource group can manage WWN groups on XP512/XP48 storage subsystem. The Modify WWN Group window (see Figure 10-17) enables you to create, modify, and delete WWN groups for each XP512/XP48 port. To open the Modify WWN Group window, open the Port Information window for the desired port (see section 10-3-1 ), and click the Modify WWN Group button.
235
Figure 10-17 Modify WWN Group window The Select WWN Group drop-down list box enables you to select the desired WWN group. The DELETE THIS GROUP button enables you to delete the selected WWN group. The CREATE NEW GROUP button enables you to create a new WWN group to the selected port. The Unsecured list box displays the WWN(s) that can be added to the selected WWN group. The Secured list box displays the WWN(s) in the selected WWN group. The ADD>> button moves the selected WWN(s) to the Secured list. The << REMOVE button moves the selected WWNs to the Unsecured list. The SAVE button saves your changes on this window and returns you to the Port Information window.
10-3-3-1 Creating a WWN group

To create a new WWN group: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. In the Physical View, select the desired port (for XP512/XP48 port CL1-A, click A in Cluster 1) to open the Port Information window. 4. Click the MODIFY WWN GROUP button to open the Modify WWN Group window (see Figure 10-17). 5. Click the CREATE NEW GROUP button, enter the name for the new WWN group, and click the OK button. The name must be no more than 8 bytes in length. You can use only the following characters for the name: A-Z a-z 0-9 ! # $ % & ' ( ) + - . = @ [ ] ^ _ ` { } ~ LUN group names are case-sensitive. You cannot enter a name that is already in use. 6. In the Modify WWN Group window select the desired host WWN(s) in the Unsecured list, and select ADD>> to move the selected WWN(s) to the Secured list. If necessary, use the << REMOVE button to move WWN(s) back into the Unsecured list.
236
Performing storage subsystem operations 7. When the Secured list displays the WWN(s) that you want to add to the WWN group to be created, click the SAVE button to add them to the new WWN group, or click the CANCEL button to cancel your request. 8. When the confirmation window displays, select the YES button to create the new WWN group, or select the NO button to cancel your request.
10-3-3-2 Modifying a WWN group

To modify an existing WWN group: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. In the Physical View, select the desired port (for XP512/XP48 port CL1-A, click A in Cluster 1) to open the Port Information window. 4. Select the desired WWN group, and use the ADD>> and <<REMOVE buttons to add WWN(s) to and remove WWN(s) from the selected WWN group. To change the name of a WWN group, enter the new name in the Select WWN Group field. 5. When the Secured list displays the desired WWN(s) for the selected WWN group, click the SAVE button to modify the WWN group, or click the CANCEL button to cancel your request. 6. When the confirmation window is displayed, select YES to modify the WWN group, or select NO to cancel your request.
10-3-3-3 Deleting a WWN group

To delete a WWN group: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. In the Physical View, select the desired port (for XP512/XP48 port CL1-A, click A in Cluster 1) to open the Port Information window. 4. Click the MODIFY WWN GROUP button to open the Modify WWN Group window (see Figure 10-17). 5. Select the desired WWN group, and click the DELETE THIS GROUP button. 6. When the confirmation window displays, click YES to delete the WWN group, or click NO to cancel your request. If you click YES, the WWN group to be deleted is no longer displayed on the Modify WWN Group window. 7. Click the SAVE button on the Modify WWN Group window to continue, or click the CANCEL button to cancel your request. 8. When the confirmation window is displayed, click YES to delete the WWN group. To cancel your request to delete the WWN group, click NO on the confirmation window, and then click the CANCEL button on the Modify WWN Group window.
237
10-3-4 Configuring Fibre Channel adapters (XP1024/XP128 and XP512/XP48)

CAUTION: Before changing the setting of a channel adapter, make sure that the following conditions are met: The storage subsystem is equipped with channel adapters capable of high-speed mode You are aware of the impact of changing the setting You understand the procedure for connecting hosts to a channel adapter in high-speed mode. Users with Modify permission who are assigned to the All Resources resource group can configure Fibre Channel adapters on the XP1024/XP128 and XP512/XP48 storage subsystems. There are three types of Fibre Channel adapters for the XP1024/XP128: 4-port, 8-port, and 16-port. You can set the fibre printed circuit board (PCB) mode only for 4-port Fibre Channel adapters. The default channel adapter mode is Standard mode. High-speed mode provides faster access speed by using more processors to handle data access. However, high-speed mode limits the number of available ports on the channel adapter card (one port for XP1024/XP128, half of the ports for XP1024/XP128). Servers or switches attached to these ports must be changed for this configuration. Once the storage subsystem and attached servers or switches are configured for high-speed mode, you can use Device Manager to change the mode of the channel adapter. For more information on the channel adapter settings, refer to the HP StorageWorks XP LUN expansion/XP Virtual LVI/LUN (VLL) and Volume Shredder user guide. To configure the speed mode of the Fibre Channel adapters in the XP1024/XP128 or XP512/XP48 storage subsystem: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. Click the Port Controllers button to open the Port Controller window (see Figure 10-18).
238
Figure 10-18 Changing the channel adapter mode (XP1024/XP128) 4. Make the desired Fibre PCB mode changes for the channel adapter, and then select OK. When the confirmation window appears, review the changes carefully. Select YES to change the modes as specified, or select NO to cancel your request. 5. If you selected YES, a message is displayed to warn you that you cannot change the Fibre PCB mode while I/O operations with the host are underway. After reviewing the information displayed in the warning message and stopping the hosts, select OK. To cancel your request to change the Fibre PCB mode, select CANCEL. 6. When you are notified that the channel adapter mode change operation is complete, reboot the host.
10-4 LDEV operations

Device Manager LDEV operations include:
Allocating storage (see section 10-4-1 ) Unallocating storage (see section 10-4-2 ) Creating an LDEV (see section 10-4-3 ) Deleting an LDEV (see section 10-4-4 ) Setting a command device (see section 10-4-5 )
To perform an operation on an LDEV for XP24000/XP20000, use the Physical View for XP24000/XP20000 (see section 10-2-1 ). To perform an operation on an LDEV for XP12000/XP10000/SVS200, use the Physical View for XP12000/XP10000/SVS200 (see section 10-2-2 ).
239
10-4-1 Allocating storage (adding volume paths)

Users with Modify permission who are assigned to the All Resources resource group can allocate storage. When you allocate storage, you assign one or more access paths (specifying ports and LUNs) to LDEV(s). You also can secure the new LUN(s) to host WWN(s) and/or, allocate LDEVs that are unallocated or already allocated. You cannot assign paths to LDEVs in the following cases:
For XP1024/XP128 A path is already set from the same LDEV with the same security. For storage subsystems other than the above A path is already set from the desired LDEV.
NOTE: A path cannot be assigned to an LDEV whose volume attribute is POOL, OnDemand, or Migration-reserved.
To allocate storage: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. NOTE: You can also allocate storage by starting from the All Storage or My Storage object (see section 8-4 ). Under the All Storage or My Storage object, select the desired storage subsystem, and then select the Open-Allocated or Open-Unallocated group. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. Open the LDEV Information window for the array group that contains the LDEV(s) that you want to allocate (see section 10-2-5 ). 4. Select the desired LDEV, and then select ALLOCATE to open the Add Storage wizard. 5. Define Host/Port Connections Step. The Define Host/Port Connections window (see Figure 10-19) enables you to select the desired port(s) and (optionally) the desired host WWN(s) to secure to the LDEV. After defining the port(s) and host/port connection(s), select NEXT to continue. NOTE: For XP1024/XP128, the following ports are not displayed: CL1-S, CL1-T, CL1-U, CL1-V, CL1-W, CL1-X, CL1-Y, CL1-Z, CL2-S, CL2-T, CL2-U, CL2-V, CL2-W, CL2-X, CL2-Y, CL2-Z. NOTE: Check boxes for ports other than Fibre Channel ports become inactive and cannot be selected. IMPORTANT: WWN groups can also be set as a security option for XP512/XP48. When a WWN group is set as a security option, all the WWNs in that WWN group are applicable.
240
Figure 10-19 Allocating storagedefining host/port connections 6. The Assign Host/Port Connections window (see Figure 10-20) enables you to assign the LDEV to the desired port(s) and/or host/port connection(s). After assigning the desired connection(s), click the NEXT button to continue.
Figure 10-20 Allocating storageassigning host/port connections
241
Performing storage subsystem operations 7. Assign LUNs Step. The Assign LUNs window (see Figure 10-21) enables you to assign the desired LUN to each new path. You can use the selected LUN or select the desired LUN for each path. After assigning the desired LUN(s), click the FINISH button to continue. For XP512/XP48, the newly assigned LUN can be registered to a LUN group just by specifying the port in step 6. Select the LUN group to which you want to register the LUN from the drop-down list displayed in the Assign LUNs window.
Figure 10-21 Allocating storageassigning LUNs 8. Summary of Changes Step. The Summary of Changes window (see Figure 10-22) displays the requested allocate storage operations and asks you to confirm the requested operations. If you need to make any changes, click the BACK button to return to the previous window (s). Click the CONFIRM button to add the specified path(s) to the LDEV, or click the CANCEL button to cancel your request to allocate storage.
242
Figure 10-22 Allocating storageconfirmation
10-4-2 Unallocating storage (removing volume paths)

Users with Modify permission who are assigned to the All Resources resource group can unallocate storage. When you unallocate storage, you remove one or more access paths from an LDEV. When you unallocate a LUSE volume, you can also optionally delete the LUSE volume to make the individual LDEVs available for use. For the XP1024/XP128, you cannot unallocate the last volume path from a logical device that is specified as a copy pair volume. For the XP512/XP48, you cannot unallocate the last volume path from a logical device that is specified as a command device or as a copy pair volume. If you want to unallocate LUNs for more than one LDEV/LU, use the Open-Allocated group for the storage subsystem (see section 8-5 ). If you use Physical View, you can unallocate LUNs only for one LDEV at a time. To unallocate storage: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. NOTE: You can also unallocate storage by starting from the All Storage or My Storage object (see section 8-5 ). Under the All Storage or My Storage object, select the desired storage subsystem, and then select the Open-Allocated group. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem.
243
Performing storage subsystem operations 3. Open the LDEV Information window for the array group that contains the LDEV(s) that you want to unallocate (see section 10-2-5 ). 4. Click the Path Info tab. Select the desired LDEV, and then select UNALLOCATE. If you started from All Storage/My Storage, you can select multiple LDEVs to unallocate (see section 8-5 ). 5. When the confirmation window is displayed, click the YES button to delete the specified path(s), or click the NO button to cancel your request to unallocate storage. 6. If you selected LUSE volume(s), Device Manager enables you to keep or delete the LUSE volume(s). Click the DELETE LUSE button to delete the LUSE volume(s) and the path(s), or click the KEEP LUSE button to keep the LUSE volume(s) and delete only the path(s). You are notified when the unallocate storage operation is complete.
10-4-3 Creating an LDEV

Users with Modify permission who are assigned to the All Resources resource group can create an LDEV on an array group. When you create an LDEV, you select an existing array group with free space and specify the desired LDEV parameters: device size and emulation type for XP1024/XP128 and XP512/XP48. Device Manager automatically adds the new LDEV to the Open-Unallocated group for the storage subsystem (in All Storage or My Storage). Logical devices created using web client are formatted when they are created. CAUTION: While the restore processing of an XP512/XP48 storage subsystem is underway using XP RAID Manager, logical device creation on that XP512/XP48 will result in an error. Logical device creation must not be executed while restore processing is underway using XP RAID Manager. CAUTION: For the XP1024/XP128 and XP512/XP48 subsystems, you can create an LDEV that is a standard LU, or you can create a custom-size LDEV that is smaller than the standard LU (minimum capacity 36 MB). Table 10-2 lists the maximum capacities for the standard LU types on the XP1024/XP128 and XP512/XP48 storage subsystems. NOTE: LUSE volumes, which are larger than standard LU types, are created from existing unallocated LDEVs (see section 7-6-2 or section 8-6 ). CAUTION: For the XP1024/XP128 and XP512/XP48 storage subsystems, you cannot create an LDEV whose size is the same size as the maximum size of free space in an array group because a control area is also created in the storage subsystem. At least 30 MB of free space must be left available. In addition to the emulation types, XP1024/XP128 supports another emulation type called OPEN-V that enables you to create a logical device whose size is (maximum size of free spacesize required for the control area). The size required for the control area depends on the size of the volume to be created (maximum of 200 MB). For OPEN-V, the minimum capacity of an LDEV that can be created is 48 MB. Table 10-2 shows maximum capacities for standard LU types. Table 10-2 Maximum capacities of standard LU types LU Type
Maximum Capacity
OPEN-K
1788 MB
OPEN-3
2347 MB
OPEN-8
7007 MB
OPEN-9
7042 MB
OPEN-E
13893 MB
NOTE: The XP1024/XP128 and XP512/XP48 storage subsystems may not support the same LU types. Some LU types are not available on some platforms.
244
Performing storage subsystem operations Device Manager uses the following conventions for capacity values:
KB = 1024 bytes MB = 1024 KB GB = 1024 MB TB = 1024 GB
To create a new LDEV: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. Open the LDEV Information window for the array group in which you want to create a new LDEV (see section 10-2-5 ):
For XP1024/XP128, select Array Groups, select View on the desired frame, select the
desired parity group on the Frame Information (level 1) window, and then select the desired array group on the Frame Information (level 2) window.
For XP512/XP48, select Array Groups, select View on the desired frame, and then
select the desired array group on the Frame Information window. 4. On the LDEV Information window for the desired array group (any tab), select the CREATE LDEV button. 5. For XP1024/XP128 and XP512/XP48, the Create LDEV window opens (see Figure 10-23). Enter the desired parameters, and then click the OK button.
For XP1024/XP128 and XP512/XP48, select the device emulation type, and enter the
desired device size (see Table 10-2). The size cannot be larger than the size of the selected device type, except for OPEN-V (refer to the HP StorageWorks XP LUN expansion/XP Virtual LVI/LUN (VLL) and Volume Shredder user guide).
245
Figure 10-23 Creating an LDEVspecifying LDEV parameters (XP512/XP48) 6. When the confirmation window is displayed, select YES to create the LDEV, or select NO to cancel your request to create the LDEV. You are notified when the operation is complete and the LDEV ID of the new LDEV is displayed. The new LDEV is displayed on the LDEV Information window and is also listed in the Open-Unallocated group for the storage subsystem (under All Storage or My Storage).
10-4-4 Deleting an LDEV

CAUTION: The delete LDEV operation is destructive. Data on the LDEV you are deleting will be lost. You should back up data before performing this operation.
Users with Modify permission who are assigned to the All Resources resource group can delete LDEVs. When you delete an LDEV, the free space in the array group increases by the size of the LDEV deleted. The following LDEVs cannot be deleted:
An LDEV to which a volume path is assigned An LDEV used as a command device An LDEV specified as a copy volume (P-VOL, S-VOL, or SP-VOL)
To delete an LDEV: 1. Make sure that the LDEV to be deleted is no longer in use, that the data has been backed up, and that all access paths to the LDEV have been removed. 2. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area.
246
Performing storage subsystem operations 3. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 4. Open the LDEV Information window for the array group in which you want to delete an LDEV (see section 10-2-5 ):
For XP1024/XP128, select Array Groups, select View on the desired frame, select the
desired parity group on the Frame Information (level 1) window, and then select the desired array group on the Frame Information (level 2) window.
For XP512/XP48, select Array Groups, select View on the desired frame, and then
select the desired array group on the Frame Information window. 5. On the LDEV Information window for the desired array group, select the desired LDEV, and then select the DELETE LDEV button. If a path to the LDEV exists, the DELETE LDEV button is not available. 6. When the confirmation window is displayed, select YES to delete the LDEV, or select NO to cancel your request to delete the LDEV. 7. Device Manager displays a warning message. Check the warning message carefully. If it is acceptable to delete the LDEV and lose the data, select the OK button. To cancel your request to delete the LDEV, click the CANCEL button.
10-4-5 Setting or canceling a command device

Users with Modify permission who are assigned to the All Resources resource group can set and cancel a command device on a StorageWorks XP Disk Array. A command device is an LU dedicated to communication between the XP RAID Manager software installed on the host and the StorageWorks XP Disk Array storage subsystem. XP RAID Manager allows you to issue XP Business Copy Software, XP Continuous Access Software, and XP Data Retention Utility commands from the host to the storage subsystem through the command device. If you are setting a command device on XP1024/XP128 or XP512/XP48, you can also set security for the command device. This LUN security setting allows you to limit the logical devices that can be used as a command device to ones that are identified by the host and to prevent unwanted access from the server host(s) using the device. Conditions the logical device must meet: To specify a logical device as a command device, the logical device must satisfy the following conditions:
For the XP1024/XP128 and XP512/XP48:
A volume path must be assigned to the logical device (XP512/XP48 only). The logical device must not be reserved for XP Auto LUN Software (XP1024/XP128 or
XP512/XP48).
The emulation type must be an OPEN- x type, such as OPEN-3 (not 3390-3C). There is no limitation on the number of command devices per storage subsystem.
To set or cancel a command device: 1. In the Explorer menu, select Resources and then Subsystems and then select the desired storage subsystem in the navigation area. 2. In the subsystem-name subwindow, click the Physical View button to display the Physical View for the storage subsystem. 3. From the Physical View, open the LDEV Information window for the array group containing the LDEV that you want to set or cancel as a command device (see section 10-2-5 ). 4. On the LDEV Information window, select the logical device that you want to set or cancel as a command device, and click the LDEV CONFIG button to open the LDEV Configuration window.
247
Performing storage subsystem operations 5. To set the device as a command device, select the Use this LDEV as a command device check box. To cancel a command device, clear the check box. 6. XP1024/XP128 and XP512/XP48 only: To set security for the command device, select the Assign Command Device Security check box. To cancel the security setting, clear the check box. NOTE: For the XP512/XP48, you can specify command device security only while you are setting a command device. You cannot modify the command device security separately from a command device. To modify security for a device that has already been defined as a command device, you must first cancel its setup as a command device, and then modify the security when you reset the command device. 7. Click the OK button to save your changes and close the LDEV Configuration window, or click the CANCEL button to close the LDEV Configuration window without saving any changes. When the command device operation is finished, Device Manager displays a confirmation window.
248
Performing report operations
11 Performing report operations

This chapter describes the different types of Device Manager reports that can be run:
Overview of Device Manager reports (see section 11-1 ) Physical configuration of the storage subsystem report (see section 11-2 ) Storage utilization by host report (see section 11-3 ) Storage utilization by logical group report (see section 11-4 ) Users and resource groups report (see section 11-5 ) LDEV details report (see section 11-6 )
11-1 Overview of Device Manager reports

Users assigned to the All Resources resource group can perform report operations. Users assigned to a user-defined resource group cannot access this function. To access reports, select Reports in the Explorer menu. The Reports subwindow in the application area lists and provides access to the Device Manager reports from which you can select the type of the report to be output. The Device Manager provides the following reports:
Physical configuration of storage subsystem Storage utilization by host Storage utilization by logical group Users and resource groups Detailed Array Reports
Reports other than Detailed Array Reports are available as an HTML or CSV file. You can choose either of the following formats for CSV reports:
A format that uses double quotation marks to enclose each value This format is supported in Device Manager version 5.6 and later. A format that does not use double quotation marks to enclose each value This format is compatible with Device Manager versions earlier than 5.6.
To change the format, you must set the properties file related to web client. For details about how to set the properties file, see the manual HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. Detailed Array Reports are available only as a CSV file in which each value is enclosed in double quotation marks ("). NOTE: To use the Physical Configuration of Storage Subsystem report, Storage Utilization by Host report, or Storage Utilization by Logical Group report, select storage subsystems so that the number of LDEVs does not exceed 10,000. If the number of LDEVs exceeds 10,000, you might not be able to display the report. NOTE: Regarding Unicode (UTF-8) for CSV reports: Device Manager uses the Unicode (UTF-8) code system to output reports in CSV format. If the output CSV file contains multi-bytes characters and is imported to a spreadsheet program that does not support Unicode (UTF-8), the output information may contain encoding errors. In such a case, open the file with a program that supports Unicode (UTF-8), such as Windows Notepad, and then convert it to the appropriate character code system.
249
NOTE: If you repeat CSV output for the report facility, the font size on the web browser may change. This has no adverse effect on the program, and you can continue operations. NOTE: When you click the HTML button in the subwindow that outputs the Storage Utilization by Host report or Storage Utilization by Logical Group report, the page might not be found. If this happens, reduce the number of storage subsystems selected, and then generate the report, or, you can increase the maximum value of the memory heap size. For information about changing the heap size for memory used by the Device Manager server, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide.
11-2 Physical configuration of the storage subsystem report

The Physical Configuration of Storage Subsystem report provides detailed information on the physical configuration of each storage subsystem added to the Device Manager server.
The HTML report outputs the storage subsystem's configuration and components. The CSV report outputs the detailed storage subsystem information as comma-separated values.
11-3 Storage utilization by host report

The Storage Utilization by Host report outputs storage utilization statistics and detailed storage information for each host added to the Device Manager server.
The storage utilization statistics for each host include capacity (GB) currently in use by host operating system(s) and percentage of capacity in use by host(s). The storage information for each host includes allocated storage that is output by storage group and LUN.
NOTE: The host agent provides the storage utilization statistics. If the Device Manager agent is not installed on a host, Device Manager cannot acquire the storage utilization statistics for the storage accessed by the host.
11-4 Storage utilization by logical group report

The Storage Utilization by Logical Group report outputs the following information:
For each storage subsystem added to the Device Manager server:
Storage subsystem name Model, serial number IP address Configured capacity Allocated capacity Percentage of allocated capacity in use by the host OS(s)
For each logical group created to the Device Manager server: group name and level, capacity, and percentage of capacity in use by the host OS(s)
NOTE: The host agent provides the storage utilization statistics. If the Device Manager agent is not installed on a host, Device Manager will not receive utilization data for the storage accessed by that host.
250
11-5 Users and resource groups report

A logged-in user with Admin permission can generate, the Users and Resource Groups report which outputs the following information for the Device Manager users:
Resource groups managed by the Device Manager server Number of users assigned individual resource groups Properties of each user (user ID, full name, description)
11-6 LDEV details report

You can create, download, and view a detailed report on the LDEVs in each storage subsystem that has been added to the Device Manager server. To create and download an LDEV details report: 1. In the Explorer menu, select Reports. The Reports subwindow appears in the application area. 2. In the Reports subwindow, select Detailed Array Reports. A list of detailed array reports appears in the application area (see Figure 11-1). The subwindow displays only the reports that the logged-in user has created.
Figure 11-1 Reports subwindow (A list of detailed array reports) 3. Click the Create Report button. The Create Detailed Array ReportReport dialog box appears (see Figure 11-2).
251
Figure 11-2 Create Detailed Array ReportReport dialog box 4. In the Create Detailed Array ReportReport dialog box, select a storage subsystem for which you want to create a report. 5. In the Detailed Array Report name text box, enter a name for the report you are creating. The name cannot exceed 32 bytes. You can use the following characters in the name: A to Z, a to z, 0 to 9, hyphen (-), underscore (_) If you do not specify a name, the report will automatically be assigned a name in the following format: DetailedArrayReport-YYYYMMDDhhmmss-nn The YYYYMMDDhhmmss part is replaced with the report creation date and time in the local time of the server. The nn part is replaced with a sequence number starting at 00 to distinguish multiple reports created within one second. 6. Click the OK button. If you want to cancel creation of the report, click the Cancel button. When you click the OK button, creation of the report starts. If a report with the name you entered already exists, a dialog box asking whether you want to overwrite the existing report appears. NOTE: You cannot create a new report when there is a report in the Processing status. If you click the OK button in the Create Detailed Array ReportReport dialog box when there is a report in the Processing status, a warning message appears under Subsystem List in the dialog box. 7. In the list of detailed array reports, check the report status. One of the following statuses is displayed for each report: Processing Indicates that the report is being created. When a report is in this status, the icon for canceling creation of the report is displayed on the left of the report name. If you click the icon, a dialog box asking you to confirm the cancellation appears. Completed Indicates that the report has been created successfully. When a report is in this status, the icon for downloading the report is displayed on the left of the report name. You can click this icon to download the report.
252
Performing report operations Incompleted Indicates that the server was forcibly terminated during creation of the report and that the report has not been completed. When a report is in this status, the icon for downloading the report is displayed on the left of the report name. If you click the icon, you can download the report up to the point when the creation was canceled. Error Indicates that an error occurred during creation of the report and that the report has not been completed. When a report is in this status, the icon for downloading the report is displayed on the left of the report name. If you click the icon, you can download the report up to the point when the creation was canceled. To view detailed information about the error, click the link. Canceled Indicates that the user canceled creation of the report. When a report is in this status, the icon for downloading the report is displayed on the left of the report name. If you click the icon, you can download the incomplete report. If you click the icon, you can download the report up to the point when the creation was canceled. NOTE: The contents of the list of detailed array reports are automatically refreshed every 15 seconds. You can refresh the contents manually by clicking the Update Status button. 8. In the list of detailed array reports, click the icon for the report you want to download. A dialog box for downloading the report appears. 9. Read the message displayed in the dialog box, and click the Save button. The Save As dialog box appears. 10. In the Save As dialog box, specify the folder in which you want to save the report, and then save the report. 11. In the list of detailed array reports, delete unnecessary reports. To do this, select the check boxes for the reports that you want to delete, and then click the Delete Report button. A dialog box asking you to confirm the deletion appears. When you click the OK button, the selected reports are deleted. If you want to cancel the deletion, click the Cancel button.
253
Troubleshooting
12 Troubleshooting
This chapter describes Device Manager web client troubleshooting.
For general information on troubleshooting, see section 12-1 . For information on countermeasures, see section 12-2 . For information on warning messages output from Device Manager, see section 12-3 . For information on error messages, see section 12-4 .
12-1 Troubleshooting operations

If there is a problem with the Device Manager web client interface, first make sure that the problem is not being caused by the PC or LAN hardware or software, and then restart the PC.
12-2 Countermeasures
If you are having trouble with Device Manager web client, first make sure the problem is not occurring at the Device Manager server. For more information on server problems, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. IMPORTANT: Make sure to read the Device Manager Release Notes. Make sure that only one Device Manager server is actively managing a single storage subsystem. If you use the storage logical partition function, one Device Manager manages one SLPR. For details about the storage logical partition function, see section 4-6-2 . Table 12-1 provides general troubleshooting information for Device Manager web client. In general, difficulties installing and running the web client can be due to problems with the Java Web Start software and/or with proxies on the local network. Table 12-1 General troubleshooting information No. Problem
1 Cannot find the Device Manager server login window.
Description
Make sure that the Device Manager server system and software are up and running. When running the web client on the same system as the Server, a potential hazard is the resolution of the host "localhost". Generally "localhost" resolves to the loopback address (127.0.0.1), which can cause problems for the Java Web Start software. Use the primary local IP address instead.
254
Troubleshooting
Table 12-1 General troubleshooting information No. Problem

2 Cannot load the Device Manager server home page. Error message: "The requested item could not be loaded by the proxy. Proxy server's network connection was refused by the server: IPaddress:port-number. The server may not be accepting connections or may be busy. Try connecting again later."
Description
If the browser may have a proxy server, it may have a proxy in place that is not allowing the traffic to go through. For Internet Explorer: 1 Select Tools, Internet Options, select Connections, select LAN Settings button, then click the Advanced button on Local Area Network (LAN) Settings. 2 In the Exceptions section, enter the IP address of the Device Manager server (123.456.78.9). Entries must be separated by semicolons. 3 Click OK all the way out, and restart the browser. For the Mozilla browser: 1 Select Edit, Preferences, and then the Advanced category. 2 Click on to expand. 3 Select Proxies, Manual Proxy Configuration, and then View. 4 Enter the IP address in the box under Exceptions. If the browser is not set to use a proxy server, this is not the source of the problem. Look for other network connectivity issues such as firewalls and routers. Might be caused by old or partial installation of the Java Web Start software. 1 Reinstall the JWS software as described in Chapter 3. 2 Make sure the proxies in Java Web Start are configured properly: a. Start the Java Web Start Application Manager (select the JWS icon on desktop or in the Start menu, for Solaris go to the Java Web Start installation directory and enter the javaws command). b. From the File menu, choose Preferences and select the General tab to configure the proxies so Java Web Start can find the Device Manager server according to the URL used in your browser. c. Select Manual, and add the exact URL to the No Proxy Hosts box. For example, if the URL is ://localhost:<port number>, then the name in the No Proxy Hosts box must be localhost. The Mozilla specifications specify that a blank window that opens when the web browser is started from the Java GUI cannot be closed automatically. If a blank window is displayed, close it manually.
The Java Web Start software is unable to launch the Java GUI. Error message: "Unable to launch web client."
When Mozilla is used as a web browser and is started from the Java GUI, a blank window appears along with the window you opened.
The File Download window appears The Java Web Start (JWS) software may have been previously when you invoke the Java GUI. installed and removed. When JWS was removed, the association between the file extension .JNLP and the JWS application may not have been removed. When the link to the .JNLP file is selected, the operating system tries to run but does not find JWS. To resolve this situation, run the installer for JWS again (the full Java Web Start Installer).
255
Troubleshooting

6 Cannot add the storage subsystem. Failed during initialization (was unable to find the device). Description: Attempt to add the storage subsystem fails and this error message is displayed: "Initialization of the SNMP connection at IP-address IP-address has failed"
Description
On the machine on which the Device Manager server is running, send a ping command to the IP address of the storage subsystem to make sure that the storage subsystem is running. Verify the SNMP configuration on the SVP, and make sure that the correct community name is specified in Device Manager (this should match the community name entered when configuring the SNMP API). A common community name is public (Device Manager default). Make sure that access to the Device Manager server IP address is not limited on the storage subsystem. For further information on SNMP troubleshooting for Device Manager, see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide. For StorageWorks XP Disk Array, make sure that no other management tools (for example, XP Remote Web Console or Remote Console) are connected to the storage subsystem. Device Manager and other management tools cannot access the same storage subsystem at the same time. Make sure that StorageWorks XP Disk Array SVP is in View mode, then check for LAN problems and/or SNMP problems on the Device Manager server. see the HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide for further information on SNMP troubleshooting. The microcode level on XP512/XP48 does not support the FTP transfer mechanism. The FTP port in XP512/XP48 SVP must be enabled. To start up the FTP daemon, left click on the ftp daemon icon in task bar. NOTE: The FTP daemon is not usually running on the SVP.
Device Manager could not find (using the discovery operation) the storage subsystem.
Cannot connect to the storage subsystem.
The storage subsystem discovery processing is very slow.
10
XP512/XP48 subsystem discovery does not finish. Slow SNMP response. Cannot add/delete volume paths. Cannot convert unallocated LUs. Cannot secure/unsecure LUs.
Device Manager server may not be able to connect to the XP512/XP48 subsystem by SNMP. Contact your network administrator. The storage subsystem microcode level does not support command complete. Make sure that the XP LUN Manager feature is enabled. In XP LUN Manager, make sure that the LUN security feature is enabled.
11 12 13
256
Troubleshooting

14 Host storage domain information remains for a port to which a LUN has not been assigned.
Description
For XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128, even when an attempt to add or remove storage fails, host storage domain information might remain for a port to which a LUN has not been assigned. To prevent host storage domain information from remaining for a port, delete the host storage domain information, and then refresh the storage subsystem. Before deleting the host storage domain information, make sure that paths that belong to the target host storage domain are not being used. To delete host storage domain information, perform one of the following:
In XP Remote Web Console, use XP LUN Manager to

delete the target host storage domain.
Use the CLI to delete the target host storage domain. Use web client to delete all the paths to which the target
storage domain has been set. After deleting the host storage domain information, reassign the necessary paths. 15 The Java GUI does not receive alert Make sure that the Java Web Start software has been configured messages from the Device Manager for client/server operations (Do not use proxy) as described in server. section 3-4 . You entered the correct password, but Device Manager tells you that the password you entered was not correct. After changes are made in a host configuration, the information is not applied to the window that displays the host properties. The Dynamic Link Manager button is not displayed in the Host view. Log out and then log back in to Device Manager, making sure to enter the correct password in the Login window. Always log on from this window. Do not use the Java Web Start User Authentication window. It might take some time for the Device Manager server to recognize the changes in the host configuration. Wait a while and then refresh the information in the host-name subwindow. When HDLM is installed on the host, the Device Manager server receives notification from a Device Manager agent and recognizes that HDLM is installed in that host. If the Device Manager server is not running when a Device Manager agent starts, the Dynamic Link Manager button is not displayed on the host-name subwindow for the host. Make sure that the Device Manager server is running, and restart the Device Manager agent. It takes a few minutes for the Device Manager server to recognize HDLM after the Agent starts. Wait for a while, and refresh the host-name subwindow. If there is too much data for an operation, the window display in the web client might fail because the HTML information cannot be received. In this case, reduce the data for operation, and then perform the operation again. When a web client machine uses the NVIDIA GeForce2 GTS video card, this problem can occur due to a problem in the video driver. If this problem occurs, move the window so that its text is off the screen, and then pull it back to the center of the screen to display it again.
16
17
18
19
The window display for the web client fails.
20
A gray window with no text or buttons is displayed.
257
Troubleshooting

21 When a Device Manager server is running in a cluster environment, a web client operation error occurs abruptly or the operation being executed result in an error.
Description
If a failover occurs when a Device Manager server is running in a cluster environment, a web client operation error occurs. In this case, log in to the web client again. If the operation being executed also results in an error and If that operation relates to the configuration modification for the storage subsystem, refresh the storage subsystem after logging in the web client again, and then check the operation result. In a cluster environment, when an error occurs in the active host and the standby host inherits the operation being executed, the file system information might remain in the window that displays the properties on the active host. Alternatively, in a cluster environment using Microsoft Cluster Server, when a storage subsystem is moved between the management-target hosts, the file system information might not be reflected promptly in the window that displays the host properties. If these problems occur, refresh the target hosts. Verify the Java software environment (see section 3-3 ). If necessary, remove the Java software, reboot, and reinstall the Java software. Do not use the [Esc] key while using web client. If you accidentally use the [Esc] key, click the Refresh Tree button or press F5. If a dialog box is open, close and then re-open it.
22
On the host in a cluster environment, the information about the file system displayed in the web client becomes incorrect.
23
Physical View is not displayed.
24
Web client becomes disabled after pressing the Escape [Esc] key.
25
Busy continues to be displayed in When the web client for Java applications performs the web client for Java applications. communication via a proxy server and the Device Manager server is stopped during creation or deletion of an LDEV, Busy continues to be displayed on the client despite the interruption of processing. Terminate the web client, and then restart it. When you attempt to display information about an internal volume to which an external volume is mapped, the external subsystem name is not displayed. The information about an internal LU to which an external LU is mapped is not displayed in the LDEV list. The total of the LDEV sizes displayed in the LDEV list does not match the displayed total size. The value of Split time indicated in pair information for XP24000/XP20000 or XP12000/XP10000/SVS200 differ in the web client and in XP Remote Web Console activated from Physical View. Although the connection to the Device Manager server is disconnected, the following error message is not displayed: "Lost Connection to Server." Make sure that the external subsystem is being managed by Device Manager. Also check the microcode level of the storage subsystem that uses XP External Storage Software because, if it is not supported in the connection-destination external subsystem, that external subsystem name is not displayed. When XP Flex Copy is used for XP1024/XP128, the information about internal LUs mapped to external LUs is not displayed in the list of LDEVs. When XP Flex Copy is used in XP1024/XP128, the displayed information differs because the size of the allocated volume includes the internal LUs. The display differs when the SVP time zone has been changed to a time other than the GMT. Return the SVP time zone to the initial setting (GMT). To correct the time, use the time displayed in XP Remote Web Console.
26
27
28
29
30
The error message might not be displayed under one of the following operation environment or conditions:
When using a web client in Solaris or HP-UX. When the LAN cable at the Device Manager server is
disconnected.
258
Troubleshooting

31 The settings specified by using the Java GUI are not applied to the storage subsystem configuration.
Description
If the Java GUI is closed while an operation is in progress in the Java GUI, that operation will be interrupted and the storage subsystem might not be configured as specified because only a part of the operation was processed. If an operation is interrupted, restart the Java GUI, check the configuration of the storage subsystem, and then make any necessary changes or perform a refresh. When you are using XP12000/XP10000/SVS200 that have been added by a user ID that has the partitioned storage administrator permission, BC is displayed in the Copy Type field of an LDEV for an XP Flex Copy pair. For details on XP Flex Copy, see the HP StorageWorks XP External Storage software user guide. When Device Manager deletes an XP Continuous Access Software pair, the copy status of the LDEV used as a secondary volume may remain PAIR in the storage subsystem even though the deletion appears to have finished normally in Device Manager. If this occurs, perform the following procedure: 1 For the LDEV to be used, execute the pairdisplay command for XP RAID Manager to make sure that: The volume attribute is S-VOL. The copy status is PAIR.
32
When Device Manager has not created a copy pair for an LDEV, BC is displayed in the Copy Type field for that LDEV.
33
An attempt to perform the following operations for the LDEV used as a secondary volume of a deleted XP Continuous Access Software will cause an error:
Creating a copy pair Creating or deleting LUSE

volumes
Deleting LDEVs Setting a command device
The copy status of the primary volume used for creating the pair is SMPL. 2 For the LDEV in the above status, execute the pairsplit R command for XP RAID Manager. For details about the XP RAID Manager commands, see the XP RAID Manager documentation. 34 In a Solaris environment, a character string in the title bar of the web browser is not displayed correctly. A warning dialog box is displayed indicating that the computer might not respond when an operation is performed for a sortable table. The character string may not be displayed correctly when the language setting of the web browser differs from that of Xterminal. Match the language setting of the web browser to that of X-terminal. A warning dialog box is displayed indicating that if too many lines are displayed in one page of the sortable table, script processing will take longer, and the computer might not respond. In this case, follow the direction on the dialog box to abort the script processing, close all the web browser windows of the process that displayed the warning dialog box, and then log in to Device Manager again. Then, change the number of lines that the sortable table can display per page to a smaller value. For details on how to change the number of lines that can be displayed in one page of a sortable table, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide. For details about the maximum number of lines that can be displayed in one page, see section 5-2-8 . The Japanese locale is set for the management server. Set the English locale for the management server.
35
36
The contents of a message are garbled in an English language environment.
259
Troubleshooting
12-3 Warning messages

Warning messages are displayed if you try to perform an operation from Device Manager that may affect subsequent operations, such as loss of data or input/output (I/O) from hosts. This section contains descriptions of the Device Manger warning messages.
12-3-1 User data might be deleted

If you try to perform an operation on a Device Manager server that will delete data, one of the following warning messages is displayed: For the warning message:
Data on the array group array-group-number, which is the target of this operation, will be lost. Make sure that the data is not necessary. As a result of this operation, data on these volumes will be lost. Are you sure you want to continue?
Continuing this operation will delete the data on the array group or volumes. Back up the data if necessary, and then continue the operation. For the warning message:
The data in the volume specified to be the secondary volume will be lost as a result of this operation. Please confirm.
If you continue the operation, data will be lost. Back up the data if necessary, and continue the operation.
12-3-2 An error occurs in I/O from hosts

If you try to perform an operation from Device Manager that may cause an error in I/O from hosts, one of the following warning message is displayed: For the warning message:
Confirm that no host and External port is performing I/O processing on any of the aaa. If I/O processing is being performed, the processing might terminate abnormally. Are you sure you want to continue?
Continuing this operation may affect I/O to aaa. Confirm that the hosts and external ports are not performing I/O operations on aaa, and continue the operation: For the warning message:
Make sure that I/O processing is not being performed from hosts or external ports that are using the port targeted for this operation. Performing this operation while I/O processing is being performed might damage the file system. Also, as a result of this operation, only the hosts and external ports that are set in the host storage domain aaa will be able to gain access.
Make sure that the hosts and external ports are not issuing I/O on any LUNs that use a port subject to this operation, and continue the operation. Executing the operation during I/O operation from a host or external ports may damage the file system. Also, as a result of this operation, only the host and external ports whose host storage domain is aaa become accessible to the LUNs. If you perform this operation, you may have to execute the Disconnect Volume procedure in XP Remote Web Console. For the warning message:
If the settings for this port are changed, the storage might become inaccessible to the hosts and external ports that are currently accessing the storage.
260
Troubleshooting For example, depending on hardware, the servers and HBAs may not recognize the LUNs using the subject port unless a specific host mode is selected for the port. For details on how to change the port settings, refer to the manual for the corresponding storage subsystem. For the warning message:
The mode cannot be switched if a host is currently performing I/O operation with the LUNs of the port. To proceed, shut down the host, change the mode, and then reboot the host. Are you sure you want to continue?
Confirm that the host has shut down, and continue the operation.
12-3-3 LUN security automatically takes effect

If you try to perform an operation from Device Manager that may cause an error in host I/O, the following warning message is displayed:
This operation will change the port's LUN security, which may prevent other hosts and External ports from accessing LUNs with the following ports. Are you sure you want to continue?
When LUN security takes effect, the servers and hosts that currently recognize the LUN using the subject port may no longer be able to recognize that LUN. If so, you must set LUN security for these servers and HBAs. If you perform this operation, you may have to execute the Disconnect Volume procedure in XP Remote Web Console.
12-3-4 Access from hosts is disabled

When you restart a storage subsystem to make a setting take effect, the following warning message is displayed:
The system will now be rebooted to apply the settings. I/O requests cannot be received during the reboot. If the system is being used as an external subsystem, make sure that you execute the Disconnect Subsystem operation Remote Web Console.
Confirm that the hosts are not issuing I/Os on any LUNs for the storage subsystem you are restarting, and continue the operation. If the subsystem is used as an external subsystem, make sure that you execute Disconnect Subsystem in XP Remote Web Console.
12-3-5 Data in an S-VOL (secondary volume) is incomplete

When you change pair status to SPLIT during an I/O operation on a P-VOL (primary volume), the following warning message is displayed:
If this operation is performed during I/O processing on the primary volume, the data of the secondary volume may be corrupted. Make sure that no I/O processing is being performed on the primary volume before you proceed. Are you sure you want to continue?
Confirm that the hosts are not issuing I/Os on any primary volume (P-VOL), and continue the operation.
12-3-6 Pair setting cannot be performed

When a volume specified as a copy pair is deleted, you may not be able to set a pair. In such a case, the following warning message is displayed:
Deleting pair volumes or command devices may disable later modification of the pair volume settings. Are you sure you want to continue?
Make sure that the following conditions for setting a pair are met: 261
Troubleshooting
For copy pair volumes: The host recognizes the copy pair volumes, and LUN security is set for that host. For command devices: The host that recognizes a copy pair volume also recognizes the command device, and LUN security is set for that host.
12-3-7 An internal volume to which an external volume is mapped is invalid

An internal volume mapped with an external volume may become invalid when you delete an external volume or change a security setting. The following warning message is displayed:
An assigned volume of XP External Storage Software may be invalid. Are you sure you want to continue?
Check any changes you may have made in this session. If you want to continue with this operation, you may have to execute Disconnect Volume in XP Remote Web Console.
12-3-8 Creating LUSE volumes from multiple external subsystems

When creating a LUSE volume by using internal volumes to which external volumes are mapped, the following warning message is displayed when you specify volumes from multiple external subsystems:
An attempt was made to create a LUSE with multiple external subsystems or an unknown external subsystem. (LDEV = LDEV-number)
Creating a LUSE with multiple external subsystems is not recommended. Select LDEVs with the same external subsystem.
12-3-9 Associating resources with different SLPRs

If you specify resources with different SLPRs when creating or changing a LUSE or a path, or copy pair (XP Business Copy Software), the following warning message is displayed:
If a storage resource is associated with a different storage resource, a partitioned storage administrator will not be able to manage the storage resource.
Check the settings carefully. Set them so that the SLPRs are the same.
12-3-10 Associating resources with different CLPRs

If you select volumes with different CLPRs while creating or changing a LUSE volume, the following warning message is displayed:
If volumes from different cache resources are used to create a LUSE volume, the effectiveness of the cache partition might be reduced.
Check the settings carefully to make sure they are set so that the CLPRs are the same. If you select LUSE volumes with different CLPRs when adding storage, the following warning message is displayed:
A LUSE volume that consists of volumes in different cache resources has been selected. This might reduce the effectiveness of the cache partition.
Check the settings carefully. Select LUSE volumes with the same CLPRs.
262
Troubleshooting
12-3-11 Displaying a window while updating the storage subsystem

If you try to perform an operation that will display a dialog box (or an application area or dialog box) while updating the storage subsystem, a warning message is displayed.
An operation was performed while the subsystem was being updated. The displayed information might not be the latest information.
The displayed information might not be the latest information. The information in the window and the warning message continue to be displayed until the updating finishes. If you try to perform an operation during updating, the operation might fail. Wait until update processing finishes and retry the operation.
12-3-12 Running a LUN Scan

When you try to run a LUN Scan, the following message is displayed:
Confirm that all hosts have been added into the host view before running a LUN Scan. After LUN Scan, Device Manager creates new hosts that have WWNs associated with the LUNs and have not been added into the Host View. You will need to clean up these hosts after the attributes of them are updated when the Device Manager Agent reports information about them. Are you sure you want to continue?
Check the list of hosts to make sure that all WWNs managed by Device Manager have been registered as hosts then continue to run the LUN Scan.
12-4 Error messages

Device Manager is displayed an error message when an error condition occurs. The error message includes the error code, error level (indicates the severity of the error), and error message. The error code range indicates the type of error. If an error condition occurs and you cannot solve the problem, please contact your HP support representative for assistance. NOTE: Device Manager sends all error notifications, including server errors, to Device Manager clients (such as the web client, CLI, and a third-party application).
263
Glossary
Glossary
Glossary term ACP AG AL API ACP Definition array control processor (back-end array processor on the XP1024/XP128 and XP512/XP48) array group arbitrated loop application program interface array control processor
BC BD
XP Business Copy Software basic disk
Cnt Ac-A Cnt Ac-S CHA CLI CLPR cmd dev CPU CSV CU CVS
XP Continuous Access Asynchronous Software XP Continuous Access Synchronous Software channel adapter command line interface cache logical partition command device central processing unit comma-separated value control unit customized volume size (another term for Virtual LUN)
DHCP DKC DKU
dynamic host configuration protocol disk controller (applicable to XP1024/XP128 and XP512/XP48 subsystems) disk unit
ESCON
Enterprise System Connection
264
Glossary
Glossary term FC FTP
Definition Fibre Channel file transfer protocol
GB GUI
gigabyte (1024 MB) graphical user interface
HA HBA HDD HDU HDLM HP SIM HSD HTML HTTP
high availability host bus adapter hard disk drive Hard Disk Unit Hitachi Dynamic Link Manager HP Systems Insight Manager host storage domain hypertext markup language hypertext transfer protocol
I/O ID INH IP IPF IPv4 IPv6 iSCSI
input/output identifier inhibit internet protocol itanium processor family internet protocol version 4 internet protocol version 6 internet small computer system interface
JNLP JRE JWS
java network launching protocol Java Runtime Environment Java Web Start software
265
Glossary
Glossary term KB
Definition kilobyte (1024 bytes)
LAN LDEV LDKC LU LUN LUSE LVM
local area network logical device logical disK controller logical unit logical unit number, logical unit XP LUN Expansion, LU Size Expansion logical volume manager
MB MF-JNL MCU MPIO
megabyte (1024 KB) mainframe - journal main control unit (for XP Continuous Access Software) multipath I/O
NAS
network attached storage
OS
operating system
P-VOL PA PC PCB PG P-VOL
primary - volume port address personal computer printed circuit board parity group primary volume (for XP Continuous Access Software or XP Business Copy Software)
RAID RCU
redundant array of independent disks remote control unit (for XP Continuous Access Software)
266
Glossary
Glossary term
Definition
S-VOL SAN SAS SATA SCSI SDS SIM SLPR SNMP SP-VOL SSL SSO S-VOL SVM SVP
secondary - volume storage area network serial attached SCSI serial advanced technology attachment small computer systems interface Solstice DiskSuite Service Information Message storage logical partition simple network management protocol secondary-primary volume (for XP Business Copy Software cascade) secure socket layer single sign-on secondary volume (for XP Continuous Access Software or XP Business Copy Software) Solaris Volume Manager service processor (component of XP1024/XP128 and XP512/XP48)
TB TCP/IP THP THP-VOL TID TLS
terabyte (1024 GB) transmission control protocol/internet protocol XP Thin Provisioning Software XP Thin Provisioning Software - volume target ID transport layer security
URL
uniform resource locator
VDEV VM
virtual device Volume Manager
267
Glossary
Glossary term VPN VxVM
Definition virtual private network Veritas Volume Manager
WBEM WWN
web-based enterprise management worldwide name
XGA XML
eXtended graphics array eXtensible markup language
268
Index
Index
A
adding: storage, 185 adding host: using Device Manager agent, 178 Admin, 30 allocating to resource group: host, 95; LDEV, 95 Application bar area, 72 automatic refresh function, 212
I
installing: web client, 40
J
JNL-VOL, 27 JWS: setting up proxy, 45
L
launching: NAS Manager, 84 license information: installing, 78; viewing, 78 LUSE volume: creating with LDEVs with allocated paths, 159; creating with LDEVs with no allocated path, 160; requirements of LDEVs that constitute, 158
sort function, 74 storage: adding, 185 storage subsystem: supported function, 32 Subscriber's Choice: HP, 20 supported function: storage subsystem, 32
T
tasks required for using: XP External Storage Software, 64 technical support: HP, 20 THP pool, 27; managing, 163 THP pool volume, 27 THP volume, 27 THP volumes: managing, 168
B
built-in accounts, 31; HaUser account, 31; System account, 31
C
capacity: calculation method, 73 Changing the lock status of a user account, 92 Clearing the browser cache, 50 Clearing the Java Web start cache, 49
M
managing: storage subsystem, 32 Modify, 30
U
upgrading the Java GUI and clearing the cache, 49 user: automatic locking, 100; management, 29 User Management, 30
N
NAS Manager: launching, 84; requirements, 54
D
displayed capacity, 73 document: providing feedback, 21
O
overview: supported function, 34
V
View, 30 viewing and installing: license information, 78 viewing the Pools group, 153
E
external port, 64 external subsystem, 64; XP External Storage Software, 207 external volume, 64
P
pagination function, 74 password: conditions, 99 Peer, 30 permission, 29 properties: resource group, 97
W
warning banner message, 101 web client: installing, 40 web client operations: requirements, 40 web sites: HP, 21 WWN, 27
F
filtering function, 75; exact match specification, 75; partial match specification, 75; range specification, 75
R
requirement: LUSE volume, 158 requirements: for web client operations, 40; NAS Manager, 54 resource group, 30; properties, 97 resource groups, 30
H
help: obtaining, 20 host bus adapter: replacing, 203 HP: Subscriber's Choice for Business web site, 20; technical support, 20; web sites, 21 HP SIM, linkage with, 39
X
XP External Storage Software, 207; external subsystem, 64, 207; external volume, 64 XP Thin Provisioning Software: managing pools, 162; viewing pools, 163
S
security, 31, 99 select all function, 74 selecting a range function, 75
269

C 01389226

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

C 01389226

Uploaded by

Copyright:

Available Formats

HP StorageWorks XP Command View Advanced Edition software Device Manager user guide

Reference number: T1780-96079 Tenth Edition: February 2008

About this guide

Overview of HP StorageWorks XP Command View Advanced Edition software Device Manager

Device Manager operations

Installing the Device Manager web client

Preparing for and starting operations

Performing Device Manager system operations

Performing user management operations

Performing logical group operations 6

All Storage/My Storage operations

Performing host operations

10 Performing storage subsystem operations

11 Performing report operations

Figures and Tables

Figures and Tables

Figures and Tables

Figures and Tables

About this guide

About this guide

The following LDEV attributes can now be displayed:

About this guide

November 2006 Fifth

A character string that represents a remote command device can now be

About this guide

Table 1 Revisions Date

XP Continuous Access Journal Software copy pairs can now be created,

About this guide

Table 1 Revisions Date

Information for troubleshooting has been added.

About this guide

Table 1 Revisions Date

The following THP functions are now supported for XP24000/XP20000:

In XP24000/XP20000, XP12000/XP10000/SVS200, and XP1024/XP128, it is

The following filtering function has been expanded:

In XP24000/XP20000, functionality to identify SATA drives has been added.

In the Detailed Information-LDEV-number dialog box, the number of blocks

In XP24000/XP20000 and XP12000/XP10000/SVS200, the LDEV

In XP24000/XP20000 of microcode version 60-02-4x-xx/xx or later, it is now

About this guide

Document conventions and symbols

italics font Monospace font

Monospace, italic font

Code variables Command-line variables

Monospace, bold font

IMPORTANT: Provides clarifying information or specific instructions.

About this guide

Full name or meaning

XP Auto LUN Software Auto LUN XP (Volume Migration)

XP Business Copy Software Business Copy XP

XP Cache Residency Manager Cache LUN XP

XP Continuous Access Journal Software Continuous Access XP Journal

XP Continuous Access Synchronous Software Continuous Access XP

XP Continuous Access Synchronous Software Continuous Access XP Synchronous

XP Data Retention Utility LUN Security XP Extension

XP External Storage Software External Storage XP

XP Flex Copy Flex Copy XP

About this guide

Table 3 Conventions: Abbreviations Abbreviation

Full name or meaning

XP LUN Expansion LUN Configuration and Security Manager XP (LUN Expansion)

XP LUN Manager LUN Management