hp_diskcachepartitionug rootsan technologies pvt ltd

8/6/2019 hp_DiskCachePartitionUG Rootsan technologies Pvt Ltd

1/34

HP StorageWorksXP Disk/Cache Partition user guide

Part number: T1722-96007Sixth edition: June 2006


2/34

Legal and notice information

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

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Governmentunder vendors 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 expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., and the Hitachi Data Systems design mark is a trademark andservice mark of Hitachi, Ltd.

UltraNet Storage Director is a registered trademark or trademark of Computer Network Technology Corporation (CNT).

HP-UX is a registered trademark of Hewlett-Packard Company.

AIX, ESCON, IBM, S/390 and z/OS are registered trademarks or trademarks of International Business Machines Corporation.

Microsoft, Windows, and Windows NT are registered trademarks or trademarks of Microsoft Corporation.

Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation in the U.S. and other countries.

Java, Sun, and Solaris are registered trademarks or trademarks of Sun Microsystems, Inc.

UNIX is a registered trademark of The Open Group in the United States and other countries.

XP Disk/Cache Partition user guide


3/34

XP Disk/Cache Partition user guide 3

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Supported storage platforms and firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6HP web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Overview of XP Disk/Cache Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9XP Disk/Cache Partition features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Cache logical partitions (CLPRs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Storage management logical partitions (SLPRs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Partition administration and administrator rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Accessing XP Disk/Cache Partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Working with CLPRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Creating CLPRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Deleting CLPRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Migrating parity groups in CLPRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4 Working with SLPRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Administering SLPRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Creating SLPRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Deleting SLPRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Migrating an SLPRs resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Displaying error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Notes, restrictions, and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

CLPRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31SLPRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figures

1 Example of a CLPR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Example of an SLPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Partition Definition pane (initial pane or Subsystem selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Partition Definition pane (CLPR selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Partition Definition pane (SLPR selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Tables1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Capacity for data in a hard disk drive associated with a CLPR and standard cache capacity . . . . . . . . 103 Command View user group permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 XP Remote Web Console mapping to Command View users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 XP Remote Web Console and Command View default users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 General troubleshooting for XP Disk/Cache Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Contents


4/34

4


5/34


6/34

6

Document conventions and symbols

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

IMPORTANT:Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

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

Collect the following information before calling:

Technical support registration number (if applicable) Product serial numbers Product model names and numbers Error messages Operating system type and revision level Detailed, specific questions

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

Subscription serviceHP recommends that you register your product at the Subscribers Choice for Business web site:http://www.hp.com/go/e-updates .

Table 1 Document conventions

Convention Element

Blue text:Table 1 Cross-reference links and e-mail addresses

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

Bold text Keys that are pressed Text typed into a GUI element, such as a box GUI elements that are clicked or selected, such as

menu and list items, buttons, and check boxes

Italic text Text emphasis

Monospace text File and directory names System output Code Commands, their arguments, and argument values

Monospace, italic text Code variables Command variables

Monospace, bold text Emphasized monospace text
http://www.hp.com/support/http://www.hp.com/go/e-updates/http://www.hp.com/go/e-updates/http://www.hp.com/support/


7/34


After registering, you will receive e-mail notification of product enhancements, new driver versions,firmware updates, and other product resources.

HP web sitesFor additional information, see the following HP web sites:

http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/service_locator http://www.hp.com/support/manuals http://www.hp.com/support/downloads http://www.hp.com/support/rwc/manuals

Documentation feedbackHP welcomes your feedback.

To make comments and suggestions about product documentation, please send a message [email protected]. All submissions become the property of HP.
http://www.hp.com/http://www.hp.com/go/storage/http://www.hp.com/service_locator/http://www.hp.com/support/manuals/http://www.hp.com/support/downloads/http://www.hp.com/support/rwc/manuals/http://www.hp.com/support/rwc/manuals/http://www.hp.com/support/downloads/http://www.hp.com/support/manuals/http://www.hp.com/service_locator/http://www.hp.com/go/storage/http://www.hp.com/


8/34

8


9/34


1 Overview of XP Disk/Cache PartitionHP StorageWorks XP Disk/Cache Partition prevents performance degradation and data loss that occurwhen connecting multiple hosts and sharing arrays among multiple departments and multiple companies.

XP Disk/Cache Partition provides a mechanism to safeguard array configurations by isolating operationalareas. There is a possibility of changing or deleting a configuration created for a specific customer bymistake. The configuration should be protected from unrelated tasks, such as a path through which a hostis connected and performing I/O, that could interrupt work in progress.Use XP Disk/Cache Partition to partition an array into multiple virtual arrays. This helps protect databecause the virtual arrays administrator cannot access the other virtual arrays for which the administratoris responsible.

XP Disk/Cache Partition featuresXP Disk/Cache Partition has two components:

Cache logical partitions (CLPRs) Storage management logical partitions (SLPRs)

Cache logical partitions (CLPRs)If one array is shared with multiple hosts, and one host reads or writes a large amount of data, the hostsread and write data might occupy a large area in the arrays cache memory. In this situation, other hostsslow down the read/write speed because other hosts must wait to write to cache memory. To prevent thissituation, the cache logical partition function in XP Disk/Cache Partition partitions the arrays cachememory. Partitioned cache memories are used as virtual cache memories, and each of them is allocatedto each host. As a result, this prevents the situation where the specified host exclusively uses most of cachememory.

Figure 1 shows how a corporations cache memory is partitioned to three virtual cache memories. Eachvirtual cache memory is allocated to each host in the three branch offices. Branch As host is inputting andoutputting a large amount of data to or from the array. However, the read and write data of Branch Ashost does not occupy cache memory because the cache capacity that Branch As host can use is limited to

40 GB. Even if Branch As host accesses a large amount of data, the hosts of other branches do not slowdown the read/write speed because of the amount of data Branch A is accessing. The hosts of otherbranches can always use up to 40 GB of cache area.

IMPORTANT:Disk/cache partitioning for the SVS200 is limited to one SLPR and four CLPRs.


10/34

10 Overview of XP Disk/Cache Partition

The virtual cache memory that the cache logical partition function partitions is referred to as the CLPR. Formore information, seeCreating CLPRs on page 19 .

Figure 1 Example of a CLPR

To create a CLPR, allocate the parity groups to CLPR. For instructions on allocating parity groups, see Working with CLPRs on page 17 .

To create and manage a CLPR, you need user authority for the array. For more information about userauthority, see Partition administration and administrator rights on page 12 and the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200 .

To manage cache memory using the functions in Cache LUN XP or Partial Cache Residence (PCR), you canset up the cache area for Cache LUN XP and PCR in each CLPR. For more information, see theHP StorageWorks Cache LUN XP user guide for the XP12000/XP10000/SVS200 .

Capacity criteria when creating a CLPRIf you create a CLPR, use the following formula to calculate the cache capacity allocated to the CLPR.

Cache capacity (GB) = Standard cache capacity (GB) + ((Cache Residency capacity (MB) +PCR capacity MB))/2,048) x 2GB

NOTE: The PCR capacity (MB) described in the formula is the Partial Cache Residence capacity(MB). For more information about standard cache capacity, seeTable 2.

Table 2 Capacity for data in a hard disk drive associated with a CLPR and standard cache capacity

Capacity for data in CLPR to 0.7TB to 2.6TB to 8.5TB to 14.4TB to 20.3TB 20.3TB or more

Standard cache capacity 4GB 8GB 12GB 16GB 20GB 24GB


11/34


NOTE: To calculate the capacity for data in a hard disk drive associated with a CLPR, add thefollowing formulas:Number of parity groups: capacity of one disk x 3 x (3D+1P)Number of parity groups: capacity of one disk x 6 x (6D+2P)Number of parity groups: capacity of one disk x 7 x (7D+1P)Number of parity groups: capacity of one disk x 2 x (2D+2D)

NOTE: To add cache memories to the local array, install them with Standard Cache AccessModel or High Performance Cache Access Model mode. If the local array has additional printedcircuit boards (PCBs), you must use the High Performance Cache Access Model mode. For moreinformation about additional cache memories, contact your HP account support representative.

Restriction on CLPR and CU groupYou cannot allocate parity groups belonging to different CU groups to a CLPR other than CLPR0. Formore information about CU groups, see theHP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200 .

Storage management logical partitions (SLPRs) An array can be shared with multiple organizations, for example, enterprises and departments within anenterprise. Therefore, multiple administrators who belong to different organizations might manage onearray. This creates the potential for an administrator who belongs in one organization to destroy otherorganizations volumes. Furthermore, it can complicate and increase the difficulty of managing the arraybecause of an incorrect operation by an administrator and its influence on other organizations. Thestorage management logical partition function in XP Disk/Cache Partition allocates all of an arraysresources (that is, ports and CLPRs) to multiple virtual arrays. Each virtual array can be accessed by onlyits administrator. Therefore, this prevents the risk that an administrator will destroy another organizationsvolumes or leak another organizations data.

In a non-partitioned environment, a full array is considered one single partition SLPR0. After the array is

partitioned, SLPR0 becomes the unpartitioned portion of the array. Similarly, CLPR0 contains all paritygroups (PGs) and cache in the non-partitioned environment. After the array is partitioned, CLPR0 containsthe remaining PGs and cache that are not allocated to other CLPRs.

Figure 2 shows an example of when one array is partitioned into two virtual arrays. Each virtual array isallocated to two enterprises respectively. In this case, enterprise As array administrator can manageenterprise As virtual array, but cannot manage one of enterprise Bs arrays. Similarly, enterprise Bsarray administrator can manage enterprise Bs virtual array, but cannot manage one of enterprise Asarrays.



12/34


13/34


Users who have read-only access. This group consists of users who have full array access and userswho have partition-level access

Table 3 Command View user group permissions

User group Permissions

Administrators Modify all managed arrays Administer partitions Administer Command View framework

Create other usersStorageAdmins Read and modify privileges for assigned arrays/partitions only

Users Read-only privileges for assigned arrays/partitions

Table 4 XP Remote Web Console mapping to Command View users

User group Permissions Command View user group

Storage Administrator withsuper-user permissions (create usersand administer partitions)

Modify entire arrayconfiguration

Administer partitions and users Download/restore administrative

backup lists Configure XP Remote Web

Console settings (for example,client timeout values)

Administrators

Storage Administrator with generalpermissions

Modify entire array configuration StorageAdmins

Storage Partition Administrator withsuper-user permissions

Access assigned partitions only Modify partition configuration Create and manage other users

for assigned partitions only

Not applicable (new capability inthe XP Remote Web Console)

Storage Partition Administrator with

general permissions

Access assigned partitions only

Manage assigned partitions

Users

NOTE: The Command View Usersgroup is mapped to the XP Remote

Web Console Users group withmodify permissions disabled.

Table 5 XP Remote Web Console and Command View default users

User group Command View and XP Remote Web Console

Storage Administrator with super-user permissions administrator/administrator

Storage Administrator with general permissions NoneStorage Partition Administrator with super-userpermissions

None

Storage Partition Administrator with general permissions user/user

NOTE: The default, user has modify permissionsdisabled by default.


14/34

14 Overview of XP Disk/Cache Partition


15/34


2 Accessing XP Disk/Cache Partition1. Launch Command View XP or XP Remote Web Console.2. Click theInstallbutton ( ). The License Key pane appears.3. Click thePartition Definitiontab.

Figure 3 Partition Definition pane (initial pane or Subsystem selected)

Tree: Displays SLPRs in the array. The SLPR number and name appear to the right of the SLPRicon ( ).SLPRs belonging to a CU group other than the current CU group have this icon ( ) and are grayedout.

Subsystem resource list: Displays information about SLPRs belonging to the current CU group. No.: Lists line number. Item: Type of resource.Storage Partitionappears in this column Name: SLPRs number and name. Cache (Num. of CLPRs): SLPRs cache capacity and number of CLPRs in the SLPR.

NOTE: For SLPR0, the cache capacity and number of CLPRs appear as follows: Cache capacity: Value is calculated by subtracting the capacity of the cache belonging to a

CU group other than the current CU group from the cache capacity that SLPR0 has. Number of CLPRs: Value is calculated by subtracting the number of CLPRs belonging to a CU

group other than the current CU group from the number of CLPRs that SLPR0 has. Regardless ofwhich CU group is selected, CLPR0 is added as one CLPR.

Num of PGs: Number of parity groups the SLPR has.

NOTE: For SLPR0, the value is calculated by subtracting the number of parity groups belonging toa CU group other than the current CU group from the number of parity groups that SLPR0 has.


16/34

16 Accessing XP Disk/Cache Partition

Num of Ports: Number of ports the SLPR has.

NOTE: For SLPR0, the value is calculated by subtracting the number of ports belonging to a CUgroup other than the current CU group from the number of ports that SLPR0 has.

Status: If the SLPR has been edited, the status appears in the right-most column. Change: SLPRs information, such as SLPR name, has been changed. Delete: SLPR has been deleted.

Apply: Applies settings.

NOTE: You can make changes for more than one CU group before implementing the settings.

Cancel: Cancels settings that were entered or selected, and restores settings to their initial values.


17/34


3 Working with CLPRs

Figure 4 Partition Definition pane (CLPR selected)

CU: Displays the selected CUs parity groups in the CLPR resource list.

NOTE: You cannot specify the number of a CU belonging to a CU group other than the currentCU group. To change the CU group, use the drop-down list for CU groups in the upper right of theXP Remote Web Console main pane. For more information about CU groups, see theHP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200 .

Tree: Lists the arrays SLPRs and CLPRs. The SLPR number and name appear to the right of the SLPRicon ( ). The CLPR number and name appear to the right of the CLPR icon ( ).SLPRs belonging to a CU group other than the current CU group have this icon ( ) and are grayedout. CLPRs belonging to a CU group other than the current CU group have this icon ( ) and aregrayed out. You cannot select these SLPRs and CLPRs.

CLPR resource list: Displays information about the selected CLPR. No.: Lists line number. Resource Type: Type of CLPR resource.Parity Groupappears in this column.

Address: Parity groups address. If the address begins withE(for example,E1-1), the parity groupcontains external LUs. If the address begins with V (for example, V1-1), the parity group containsvirtual volumes.

Properties: For a parity group containing internal volumes of the array, the parity groups capacityand the RAID configuration appear. For a parity group containing external LUs, the external LUscapacity appears, but the RAID configuration does not appear. For a parity group containingvirtual volumes, the capacity of virtual devices (VDEVs) appears, but the RAID configuration doesnot appear.

Emulation: Parity groups emulation type. Information: If an LU is available with On Demand,On Demand appears. To make the LU

available, use the On Demand pane. See the HP StorageWorks Command View XP Advanced


18/34


Edition Device Manager Server installation and configuration guide or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200 .

Detail for CLPR: Selected CLPRs settings. You must change the CLPRs settings. CLPR Name: CLPRs name, up to 16 alphanumeric characters.

NOTE: You cannot change the name of CLPRs that have this icon ( ) and are grayed out. Tochange their names, switch the CU group using the drop-down list for CU groups in the upper rightof the XP Remote Web Console main pane.

Cache Size: CLPRs cache capacity. Must be between 6 GB and 252 GB in 2 GB increments. Thedefault is 4 GB.

Cache LUN XP Size: Cache Residencys cache capacity. Must be between 0 and 252 GB in0.5 GB increments. The default is 0 GB.

NOTE: The value you select for this CLPR must be bigger than the Cache Residency cachescapacity that has already been defined for this CLPR using Cache LUN XP. Check the size ofCache Residency that has already been defined in Cache LUN XP before changing the value.

Number of Cache LUN XP Areas: Number of Cache Residency areas. Must be between 0 and4,096. The default is 0.

NOTE: The value selected for this CLPR must be bigger than the number of Cache Residencyareas that have already been defined for the CLPR using Cache LUN XP. Check the number ofCache Residency areas that have already been defined in Cache LUN XP before changing thevalue.

Partial Cache Residence Size: Partial Cache Residences (PCRs) cache capacity. Must be between0 and 252 GB in 0.5 GB increments. The default is 0 GB.

NOTE: The value selected for this CLPR must be bigger than the total amount of Partial CacheResidence that has already been defined for this CLPR using Cache LUN XP. Check the totalamount of Partial Cache Residence that has already been defined in Cache LUN XP beforechanging the value.

NOTE: You cannot change the capacity value of CLPR0 directly. If you change another CLPRscapacity, the difference is reflected in CLPR0s capacity.

NOTE: The maximum available cache capacity (capacity of mounted cache minus total amount of

usage for other CLPRs) appears for each upper limit ofCache Size, Cache LUN XP Size, Number ofCache LUN XP Areas, and Partial Cache Residence Size.

NOTE: The remaining capacity, which is calculated by subtractingCache LUN XP Sizeand PartialCache Residence SizefromCache Size, must be 4 GB or more in CLPR0. If you changedCacheSize, Cache LUN XP Size, or Partial Cache Residence Size, verify that the capacity calculated bysubtractingCache LUN XP Sizeand Partial Cache ResidencefromCache Sizeremains 4 GB ormore in CLPR0.


19/34


NOTE: For more information about Cache LUN XP and Partial Cache Residence, see theHP StorageWorks Cache LUN XP user guide for the XP12000/XP10000/SVS200 .



Cancel: Cancels settings that were entered or selected, and restores settings to their initial values.

Creating CLPRsIf you have not yet created a CLPR, the entire cache appears in CLPR0 in the Partition Definition pane. Topartition the cache, create a CLPR. The created CLPR can be allocated to each SLPR. CLPRs can becreated in a selected SLPR.


NOTE: Only the Administrators can create CLPRs.

NOTE: If you create a CLPR, the default cache size is 4 GB. To create a CLPR, the desired cache size isallocated from CLPR0 (entire cache).

NOTE: To create a CLPR, the remaining cache size, which is calculated by subtractingCache LUN XPSizeand Partial Cache Residence Sizefrom theCache Sizeof CLPR0, must be 8 GB or more.

1. Confirm the current CU group in the drop-down list for CU groups at the top of the pane.

NOTE: To change the CU group, select the desired CU group from the drop-down list for CUgroups in the upper right of the XP Remote Web Console main pane. For more information aboutCU groups, see the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200 .

2. Right-click an SLPR in the tree, and selectCreate CLPR. The CLPR is added to the tree.3. Select a CLPR in the tree. Information about the selected CLPR appears in theDetail For CLPRsection.

NOTE: If a CLPR has this icon ( ) and is grayed out, you cannot select the CLPR. To change theCU group, return tostep 1.

4. Change CLPR settings as needed.5. ClickApply. The progress bar appears.

NOTE: Even though you clicked Apply, the parity groups have not been allocated to a CLPR yet.

6. To allocate parity groups to a CLPR, migrate the parity groups from another CLPR (seeMigratingparity groups in CLPRs on page 20 ).


20/34


NOTE: To change an existing CLPRs settings, repeatstep 3 throughstep 5.

Deleting CLPRsIf you delete a CLPR, the resources (that is, parity groups) in the CLPR are automatically returned to CLPR0.

NOTE: You cannot delete CLPR0.

1. Confirm the current CU group in the drop-down list for CU groups in the upper right of the XP Remote Web Console main pane.


2. Right-click the CLPR you want to delete in the tree, and selectDelete CLPR. The selected CLPR is deleted

from the tree.


3. ClickApply. A progress bar appears.

Migrating parity groups in CLPRsYou can migrate parity groups in a CLPR to another CLPR.

NOTE: You cannot migrate parity groups to a CLPR belonging to a CU group other than the current CPLR.

NOTE: Multiple parity groups that construct the concatenated parity group must belong to the same CLPR.

NOTE: You cannot migrate the parity group that contains the LDEVs to which the Cache Residency cacheextents is defined to another CLPR.

1. Confirm the current CU group in the drop-down list for CU groups in the upper right of the XP Remote

Web Console main pane.


2. Double-click the SLPR in the tree. CLPRs appear under the specified SLPR in the tree.3. Select a CLPR from the tree. The selected CLPRs resource list appears.


21/34



4. Right-click the parity groups you want to migrate from the CLPR, and selectCut.

NOTE: You can select the multiple parity groups.

5. Right-click the CLPR you want to migrate the parity groups to, and selectPaste Parity Group. Theselected parity groups are added to the CLPR resource list.

NOTE: You must select a CLPR that has this icon ( ) and black characters for the destinationCLPR.

6. Click Apply. The progress bar appears.


22/34



23/34


4 Working with SLPRs

Figure 5 Partition Definition pane (SLPR selected)

Tree: Displays SLPRs and CLPRs in the array. The SLPR number and name appear on the right of theSLPR icon ( ). The CLPR number and name appear on the right of the CLPR icon ( ).SLPRs belonging to a CU group other than the current CU group have this icon ( ) and are grayedout. CLPRs belonging to a CU group other than the current CU group have this icon ( ) and aregrayed out. You cannot select these SLPRs and CLPRs.

SLPR resource list: Displays information about resources in the specified SLPR (that is, CLPRs and portbelonging to the current CU group.

NOTE: If you select SLPR0 in the tree, all resources (CLPRs and ports) that have not been allocatedto any SLPRs yet appear.

NOTE: Information about CLPR0 appears regardless of which CU group is selected.

No.: Lists line number. Resource Type: Type of the SLPRs resources:Cache Partitionor Port. Name: CLPR or port name.

If the resource type isCache Partition, the CLPR number and name appear.If the resource type isPort, the port name appears.

Properties: CLPRs capacity and number of parity groups allocated to the specified CLPR.


24/34


NOTE: The number of parity groups for CLPR0 is calculated by subtracting the number of paritygroups belonging to CU groups other than the current CU group from the total number of paritygroups that CLPR0 has.

Information: Channel adapter name, if the resource type isPort. Status: If the SLPRs resources (CLPRs and ports) have been edited, the SLPRs status appears in the

right-most column. Create: A CLPR or port has been created. Delete: A CLPR or port has been deleted.

Detail for SLPR: Displays the SLPRs settings. You can change the SLPRs settings. SLPR Name: SLPRs name, up to 32 alphanumeric characters.

NOTE: You cannot change the name of SLPRs that have this icon ( ) and are grayed out. Tochange their names, switch the CU group using the drop-down list for CU groups in the upper rightof the XP Remote Web Console main pane.

CU(* in use): CU number in the specified SLPR (00 - FE). A CU number with an asterisk (*) indicates

the SSID is registered to the CU. To delete a CU from the specified SLPR and return it to the Available CUlist, select the CU from the list, and clickDelete.

NOTE: The number of a CU belonging to a CU group other than the current CU group does notappear.

Available CU(* in use): CU: Number of the CUs belonging to the current CU group. A CU number with an asterisk (*)

indicates that the SSID is registered to a CU. SLPR: SLPR to the CU belongs to. SSID(SLPR): SSID if the SSID is registered to a CU. The SLPR the SSID belongs to appears

between parentheses on the right of the SSID.To add a CU to the specified SLPR and return the CU to theCUlist, select the CU from the list,and click Add. A CU number with an asterisk (*) indicates the SSID is registered to the CU. Youcan select up to 64 CUs into which the SSIDs are registered or not.

NOTE: If users in the StorageAdmins group who have partition-level access want to use theCustomized Volume function, first specify the CU for each SLPR to prevent overlapping the newlyallocated CU numbers and the existing CU numbers in other SLPRs. If CU numbers are notspecified first, users in the StorageAdmins group who have partition-level access cannot use theCustomized Volume function.

SSID(* in use): SSID in the selected SLPR (0004 to FFFE). An SSID number with an asterisk (*)indicates the SSID is registered to the CU.

NOTE: Only SSIDs registered to a CU belonging to the current CU group appear for SLPR0.

NOTE: If a customized volume (CV) is set using the Customized Volume function, and the CUnumber and SSID are registered to different SLPRs, a dash (-) appears to the right of the SSID. Formore information, see theHP StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200 .


25/34


From: Starting number of the SSID added to the specified SLPR (0004 to FFFE). You can enter anSSID that is in SLPR0.

To: Last number of the SSID added to the specified SLPR (0004 to FFFE). You can enter up to 256SSIDs that are in SLPR0.

NOTE: To add SSIDs to an SLPR, enter the starting number inFrom, enter the last number inTo,and click Add.

NOTE: If you add multiple SSIDs to the specified SLPR, theTonumber must be smaller than theFromnumber.

NOTE: To delete an SSID from theSSIDbox, select the SSID from theSSIDbox, and click Delete.

NOTE: If users in the StorageAdmins group who have partition-level access use the Customized Volume function, first specify the SSID number for the SLPR to prevent overlapping newly allocated

SSID numbers and existing SSID numbers in another SLPR.



Cancel: Cancels settings entered or selected, and restores settings to their initial values.

Administering SLPRsOnly storage administrators can make settings for SLPR0. A storage partition administrator only hasauthority within the assigned storage logical partition. The storage administrator can also assign writepermission for one or more of the following functions:

Volume Manager LUN Security XP Extension LUN Manager Cache LUN XP Auto LUN XP

The following is the general procedure required for preparing and administering the array with SLPRs.Only Administrators can perform this procedure.

1. Create an SLPR (seeCreating SLPRs on page 26 ).

2. On the License Key Partition Definition pane, allocate licenses for software products to the SLPR (seethe HP StorageWorks Command View XP Advanced Edition Device Manager Server installation and configuration guide or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200 ).

NOTE: If software product licenses have not been allocated to an SLPR, the user assigned to theSLPR cannot use the software products. For Auto LUN XP, if the licensed capacity for the entirestorage is sufficient, the Administrator can use Auto LUN XP to monitor the entire storage, even if

Auto LUN XPs license has not been allocated to the SLPR.


26/34


3. For instructions on adding users, see theHP StorageWorks Command View XP Advanced EditionDevice Manager Server installation and configuration guide or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200 .

4. To delete an SLPR, delete all users and set the license capacity to 0 GB, or clickDisable for allsoftware products assigned to the SLPR on the License Key Partition Definition pane. SeeDeletingSLPRs on page 27 .

NOTE: You cannot migrate mainframe volumes out of SLPR0. All mainframe volume operations can be

performed by storage administrators, not storage partition administrators.

NOTE: You can assign a user to an SLPR that has not yet been created. However, if the SLPR does notexist, an error occurs when that user attempts to launch Command View AE or XP Remote Web Console.

Creating SLPRsIf you have not yet created an SLPR in the array, all of the arrays resources (that is, CLPRs and ports)belong in SLPR0. To divide the arrays resources, create a new SLPR in the array.


NOTE: Only Administrators can create SLPRs.



2. Right-clickSubsystem, and select Create SLPR.

NOTE: To create multiple SLPRs, repeatstep 2.

3. Select an SLPR from the tree (seeFigure 5).

NOTE: If an SLPR has this icon ( ) and is grayed out, you cannot select the SLPR. To change the

CU group, return tostep 1.

4. Change the SLPRs settings as needed.5. Click Apply. A progress bar appears.

NOTE: Even though you clicked Apply, the resources (CLPRs and ports) have not been allocatedto an SLPR yet.

6. To allocate resources (CLPRs and ports) to an SLPR, perform one or both of the following:a. Create a CLPR in an SLPR (seeCreating CLPRs on page 19 ).


27/34


b. Migrate a port from another SLPR (seeMigrating an SLPRs resources on page 27 ).

NOTE: To change an existing SLPRs settings, repeatstep 3 throughstep 6.

Deleting SLPRsIf you delete an SLPR, partitioned resources are automatically returned to SLPR0.

NOTE: You cannot delete SLPR0.

NOTE: Only Administrators can delete SLPRs



2. Right-click the SLPR you want to delete in the tree, and selectDelete SLPR.

NOTE: If an SLPR has this icon ( ) and is grayed out, you cannot select the SLPR. To change theCU group, return tostep 1.

3. Click Apply. The progress bar appears.

Migrating an SLPRs resourcesYou can migrate CLPRs and ports that are managed in an SLPR to another SLPR.

NOTE: You cannot migrate CLPRs and ports to an SLPR belonging to a CU group other than the currentSLPR.

NOTE: You can migrate only Target ports to another SLPR. You cannot migrate Initiator, RCU Target,and External ports.

NOTE: A NAS port belonging to the same channel adapter must belong to the same SLPR. For moreinformation, see theHP StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200 .

1. Confirm the current CU group in the drop-down list for CU groups in the upper right of the XP Remote Web Console pane.


28/34



2. Select an SLPR from the tree. The SLPR resource list appears.3. Right-click the CLPR or port you want to migrate, and selectCut.

NOTE: You can select multiple CLPRs or ports.

NOTE: To migrate NAS ports, select all ports in the same CHN (channel adapter for the NAS)and the CLPRs containing LUN0000 and LUN0001 that belong to the NAS-Sys host group, andmigrate them at the same time.

4. Right-click the SLPR you want to migrate the CLPR or port to, and selectPaste CLPRs, Ports. If youmigrated CLPRs, they are added to the tree and SLPR resource list. If you migrated ports, they areadded only to the SLPR resource list.

NOTE: You must select an SLPR that has this icon ( ) and black characters for the destinationSLPR.

NOTE: The LUN0000 and LUN0001 belonging to the NAS-Sys host group must belong to thesame SLPR as the NAS port. LUNs from LUN0005 to LUN000A in the NAS system LU must belongto SLPR0.

5. ClickApplyto apply settings. The progress bar appears.

Displaying error messagesIf settings contain a discrepancy, an error message appears when you click Apply. Even if you clickOK orCancelto close the message after seeing the error message, you can refer to the latest error message.

1. Right-click the SLPR in the tree, and selectError Detail.2. ClickOK to close the message.


29/34


5 TroubleshootingTable 6 provides general troubleshooting instructions for XP Disk/Cache Partition operations.

Table 6 General troubleshooting for XP Disk/Cache Partition

Error Corrective Action

All XP Disk/Cache Partition functions cannot beperformed. If you logged on to Command View XP or XP Remote Web Console as the storage partition administrator touse XP Disk/Cache Partition, you cannot perform anyfunctions. To use XP Disk/Cache Partition:1. Log on as the storage administrator.2. Contact the storage administrator and have that

person perform XP Disk/Cache Partition functions.

PortThe specified port cannot be migrated to another SLPR.

You can migrate only Target ports to another SLPR. Youcannot migrate Initiator, RCU Target, and Externalports. Select a Target port.

Parity groupThe parity group administered in a CLPR cannot migrateto a CLPR in another SLPR.

Only parity groups for open-system user volumes amongparity groups administered in a CLPR can migrateoutside of SLPR0. You cannot migrate parity groups formainframe volumes. Select parity groups that are not formainframe volumes.

NAS system LUThe parity group administrated in a CLPR cannotmigrate to a CLPR in another SLPR.

Parity groups that contain the NAS system LU(LUN0005, LUN0006, LUN0008, LUN0009, andLUN000A) cannot migrate outside of SLPR0. NASsystem LU (LUN0000 and LUN0001) must belong to thesame SLPR as the NAS channel adapter.Check the NAS system LUs settings, and correct thesettings if necessary. For more information aboutchanging NAS system LU settings, contact yourHP account support representative.

LUThe parity group administrated in a CLPR migrated tothe CLPR in another SLPR.

The LU in the parity group administrated in a CLPR isset across multiple SLPRs.

The NAS system LU (LUN0000 and LUN0001) doesnot belong to the same SLPR as the NAS channeladapter.

Check the settings, and migrate ports associated to theLU to the SLPR to which the parity group migrated, ifnecessary.

LU A CLPR in an SLPR migrated to another SLPR or a CLPRwas deleted.

The LU in the parity group administrated in a CLPR isset across multiple SLPRs.

The NAS system LU (LUN0000 and LUN0001) doesnot belong to the same SLPR as the NAS channeladapter.

Check the settings, and migrate ports associated to theLU to the SLPR to which the parity group migrated, ifnecessary.

LU A port that is administrated in an SLPR migrated toanother SLPR.

The LU associated to the port administrated in an SLPR isset across multiple SLPRs.Check the settings, and migrate the parity groupdefined to the LU to the CLPR defined to the SLPR towhich the LU migrated, if necessary.


30/34

30 Troubleshooting

LUSE volume A parity group that is administrated in a CLPR migratedto another CLPR.

The LUSE volume associated to the parity groupadministrated in a CLPR is set across multiple CLPRs.Check the settings, migrate the entire LUSE volume tothe CLPR to which the parity group migrated, ifnecessary.

A port in High Speed modeThe port in an SLPR migrated to another SLPR.

You are trying to allocate ports in a port block in HighSpeed mode to multiple SLPRs. Check the ports settings,and ensure that all ports in the port block belong to thesame SLPR.

Name of SLPRThe SLPR name cannot be changed.

You cannot assign the same name to multiple SLPRs.The SLPR name you entered is already used. Enteranother name.

Name of CLPRThe CLPR name cannot be changed.

You cannot assign the same name to multiple CLPRs.The CLPR name you entered is already used or reservedby a system. Enter another name.

Parity GroupThe parity group in a CLPR cannot migrate to anotherCLPR.

If you cannot migrate the parity group in a CLPR toanother CLPR. The specified parity group is concatenated to

another parity group. The parity groups thatconstruct the concatenated parity groups mustbelong to the same CLPR. Specify all parity groupsthat construct the concatenated parity groups.

If you do not click Applywhen creating a new CLPR,the parity group cannot be allocated. Click Apply,and migrate the parity group.

NAS portThe NAS ports in an SLPR migrated to another SLPR.

NAS ports in the same channel adapter must belong tothe same SLPR. Migrate all NAS ports in the samechannel adapter.

SSIDYou cannot migrate SSIDs.

You cannot migrate the SSID associated to a CU groupthat does not belong to the current CU group. In thiscase, migrate the SSID:1. Use the drop-down list for CU groups in the upper

right of the XP Remote Web Console main pane tochange the CU group to the CU group the desiredSSID is associated to.

2. Delete the SSID you want to migrate.3. Use the drop-down list for CU groups in the upper

right of the XP Remote Web Console main pane toswitch the CU group to the CU group the destinationSLPR belongs to.

4. Add the SSID.

Table 6 General troubleshooting for XP Disk/Cache Partition (continued)

Error Corrective Action


31/34


6 Notes, restrictions, and requirementsThis chapter provides additional information about using SLPRs and CLPRs.

CLPRs When creating a partition, the partitions license keys are disabled by default. Use the License Key

Partition Definition pane to enable license keys for the new partition. Basic license keys include XP Web Console and Java API. Both are required to enable the Web GUI for new partitions.

Adding or changing a CLPR definition can take several hours. To minimize the amount of timerequired when moving cache from one CLPR to another, create partitions when the arrays workload islight.

HP does not recommended the following operations with CLPRs: Creating a LUSE volume extending over multiple CLPRs. If performed, you cannot use volumes

belonging to the CLPRs to which the LUSE is set as a Continuous Access XP or TrueCopy for z/OS pair volume.

Business Copy XP Quick Restore operations affecting multiple CLPRs. Auto LUN XP manual migrations affecting multiple CLPRs.

If you perform Continuous Access XP Asynchronous or TrueCopy for z/OS Asynchronous operations,and allocate volumes that extend over multiple CLPRs to the same consistency group, you cannotcreate a pair.

If you perform Continuous Access XP Asynchronous or TrueCopy for z/OS Asynchronous operations,you can allocate only Continuous Access XP Asynchronous or TrueCopy for z/OS Asynchronous pairsbelonging to the same CLPR to one consistency group. Parity groups allocated to the CLPR that theseContinuous Access XP Asynchronous or TrueCopy for z/OS Asynchronous pairs belong to cannotmigrate to another CLPR.

The following CU groups are for mainframe volumes: CU40-7F, CU80-BF, and CUC0-FE. Therefore,you cannot use these CU groups for some program products. For more information about whether ornot you can use all CU groups, see the user guide for each program product.

SLPRs Ports being assigned to an SLPR should not have existing host groups and LUNs assigned to them.

Assign LUNs and define host groups after the partition is created. Assign LUNs for an SLPR from array groups that are assigned to control units (CUs) that have been

assigned to that SLPR. The StorageAdmin for a partition can only allocate from array groupsbelonging to the StorageAdmins assigned partition.

HP does not recommend making settings on multiple SLPRs in a single operations because it results inmore complex and difficult SLPR administration.

If an administrator forces the following functions for multiple SLPRs and contradictions occur as aresult, the StorageAdmin users ability to use the SLPR is affected: Auto LUN XP manual migration

Business Copy XP Quick Restore LU path settings High Speed mode settings Creating a LUSE volume

Mainframe volumes must be allocated to SLPR0. Before a customized volume (CV) is created, the StorageAdmins user must allocate CU numbers to the

SLPR. Allocated CU numbers are required only for defining the CU number to be allocated to the LDEVwhen the StorageAdmin user creates a CV.


32/34

32 Notes, restrictions, and requirements


33/34


Index

Aaccessing XP Disk/Cache Partition 15administering SLPRs 25administrator rights 12arrays, virtual 11audience, documentation 5

Ccache logical partitions. See CLPRsCLPRs

about 9creating 19deleting 20example of 10migrating parity groups 20restrictions on 31settings 17

conventionsdocument 6text symbols 6

customer support 6

Ddeleting

CLPRs 20SLPRs 27

displaying error messages 28document

conventions 6feedback 7prerequisites 5related documentation 5

Eerror messages 28

Ffeatures 9feedback, documentation 7firmware, supported 5

Hhelp, obtaining 6 , 7HP

storage web site 7Subscribers Choice for Business web site 6technical support 6

Iinstallation 15

Mmemory, cache 9migrating

parity groups across CLPRs 20SLPR resources 27

Ppartition administration 12prerequisites 5

Rrelated documentation 5

SSLPRs

about 11administering 25creating 26deleting 27example of 12information about 15migrating resources 27restrictions on 31settings 23

storage management logical partitions.See SLPRsstorage platforms, supported 5StorageAdmins 12Subscribers Choice for Business, HP 6supported storage platforms and firmware 5symbols in text 6

Ttechnical support, HP 6text symbols 6

Uusers, access rights of 12

Vvirtual arrays 11

W web sites

HP documentation 7HP storage 7HP Subscribers Choice for Business 6


34/34

hp_diskcachepartitionug rootsan technologies pvt ltd

Documents