hp_cachelun_xp1024ug rootsan technologies pvt ltd

8/6/2019 hp_CacheLun_xp1024UG Rootsan technologies Pvt Ltd

1/20

HP StorageWorks

Cache LUN XP user guidefor the XP1024/XP128

Part number: T1616-96002Second edition: March 2006


2/20

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. The Hitachi Data Systems design mark is a trademark and servicemark of Hitachi, Ltd.

Hitachi Freedom Storage, FlashAccess, ShadowImage, CruiseControl, Just In Time Storage, and Lightning 9900 are trademarks of Hitachi DataSystems Corporation.

S/390 is a registered trademark of International Business Machines Corporation.

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

Netscape is a trademark or registered trademark of Netscape Communications Corporation.

Solaris and Java are trademarks or registered trademarks of Sun Microsystems, 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 respectiveowners.

Cache LUN XP user guide for the XP1024/XP128


3/20

Cache LUN XP user guide for the XP1024/XP128 3

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Helpful web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Cache LUN XP for the XP1024/XP128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Supported volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Cache LUN XP tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Supported emulation types and other parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Supported emulation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Modified volume types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Unit of cache area allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Number of cache areas allowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Cache LUN XP modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Priority mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Priority mode details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10General cache capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Bind mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Bind mode details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Bind mode and RAID groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Pre-staging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Starting Cache LUN XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Cache LUN pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Prestaging check box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12LDEV tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12LDEV table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Cache LUN pie chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Cache settings section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Setting (creating) a cache extent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Releasing (removing) a cache extent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Changing an extents mode and pre-staging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figures1 Cache LUN XP operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Cache LUN pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Multi Set pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Multi Release pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Tables1 Recommended and minimum firmware versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Cache LUN XP icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Contents


4/20

4


5/20


About this guideThis guide provides information about the following:

Supported volumes on page 9

Cache LUN XP tasks on page 9

Supported emulation types and other parameters on page 9

Restrictions on page 10 Cache LUN XP modes on page 10

Pre-staging on page 11

Starting Cache LUN XP on page 12

Setting (creating) a cache extent on page 14

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

Disk array hardware and software

Data processing and RAID storage subsystems and their basic functions

NOTE: The functions described in this manual may be limited, depending on your assigned level of useraccess. Some users will have read-only access while others will have limited or full array access. Foradditional information on users and user groups, please see the HP StorageWorks XP Remote WebConsole user guide.

PrerequisitesPrerequisites for using this product include:

Installation of the HP StorageWorks disk array(s)

Installation of the license key for this product

Firmware versionsThe recommended firmware versions shown in Table 1 provide the optimal level of support for the featuresprovided with this product. Older firmware versions can be used; however, product features enabled withnewer firmware will not appear.

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

HP StorageWorks XP Remote Web Console user guide for XP1024/XP128

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

Table 1 Recommended and minimum firmware versions

XP disk array Minimum Recommended

XP1024/XP128 21-14-14-00/00 or later 21-14-18-00/00 or later
http://www.hp.com/support/rwc/manuals/http://www.hp.com/support/rwc/manuals/


6/20

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

Applicable error messages

Operating system type and revision level

Detailed, specific questions

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

Subscription serviceHP strongly recommends that customers register online using the Subscribers choice web site athttp://www.hp.com/go/e-updates.

Table 2 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 asmenu 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/20


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

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

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

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

http://www.docs.hp.com

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


8/20

8


9/20


1 Cache LUN XP for the XP1024/XP128Use Cache LUN XP to reserve areas of cache memory on the disk array for storing high-use data from theLDEVs. Data access speed is improved because the cache-resident data is available to the hosts at muchfaster transfer speeds. This can be applied to both read and write I/O operations.

Supported volumes

Cache LUN XP works with normal volumes, LUSE volumes, and custom volumes (configured through CVS).

Use custom volumes and Cache LUN XP together to achieve higher data access performance (than whenthese features are used separately).

Cache LUN XP tasksUse Cache LUN XP to perform the following tasks:

Setting (creating) a cache extent on page 14

Releasing (removing) a cache extent on page 16

Changing an extents mode and pre-staging on page 17

Figure 1 Cache LUN XP operations

Cache LUN XP requires a portion of cache memory, called the Cache LUN XP cache area. You can

change the capacity of the Cache LUN XP cache area when installing or removing cache memory.Typically, data assigned to Cache LUN XP becomes resident (staged) in cache after it is first accessed by ahost. Then, the host finds the data in cache for the second and subsequent accesses.

Another function, called pre-staging, puts data in the Cache LUN XP cache area when the data is first setup for caching. Pre-staging allows the host to find data in the cache at the first access.

Cache areas (also called cache extents) can be added or removed at any time. Each cache extent isdefined as a range of logical blocks within an LDEV or as an entire LDEV. Logical blocks are defined bystarting and ending Logical Block Addresses (LBAs).

Supported emulation types and other parametersSupported emulation types

Supported open system emulation types are OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, and OPEN-V.

Supported mainframe emulation types are 3390-3, 3390-3A, 3390-3B, 3390-3C, 3390-3R, 3390-9,3390-9A, 3390-9B, 3390-9C, 3390-L, 3390-LA, 3390-LB, and 3390-LC.

Modified volume typesLUSE (LU Size Expansion) and CVS (Custom Volume Size) volumes can be placed in the Cache LUN XPcache area.

If you want to apply Cache LUN XP to a LUSE volume, you must apply Cache LUN XP to all the LDEVs thatform the LUSE volume.


10/20

10 Cache LUN XP for the XP1024/XP128

Unit of cache area allocationA Cache LUN XP extent is a range of logical blocks within an LDEV. A logical block is 512 bytes.

For OPEN-V, a cache extent must have at least 128 Logical Block Addresses (LBAs), or 66 KB. For all othersupported open system emulation types, a cache extent must have at least 96 LBAs, or 49.5 KB. This isknown as a cache slot. A cache extent can have a maximum size of an entire LDEV, up to the limits ofCache LUN XP cache memory. Allocate data to Cache LUN XP with a minimum size of 128 LBAs forOPEN-V and 96 LBAs for other than OPEN-V.

For mainframe systems, a cache extent must be at least one cache slot or track (48 KB or 64 KB). Itsmaximum size may be an entire LDEV, up to the limits of Cache LUN XP cache memory. Allocate data toCache LUN XP in units of cylinders and tracks.

Number of cache areas allowed

In DKC: 1,024

In LDEV: 1,024

Restrictions

Cache LUN XP modes

Cache LUN XP has two modes: priority mode

bind mode

Priority modePriority mode requires fewer cache resources but has performance limitations over bind mode. Prioritymode keeps all read data in cache (until you delete the extent) but all writes are destaged to disk normally(using the same algorithms as for regular, non-Cache LUN XP data).

Priority mode details

All reads following the initial read to a block will result in cache hits (100% cache read hits).

After destaging of the write block to disk, the duplicated write areas in general cache become free.

Table 3 Restrictions

Configuration Restrictions Do not exceed the capacity of the Cache LUN XP cache.

Do not configure an Auto LUN XP reserved volume for Cache LUN XP. Do not place an LDEV in cache twice.

You cannot allocate Cache LUN XP cache space for an on-demand LDEV.

To apply Cache LUN XP to a LUSE volume, you must apply it to all the LDEVsthat form the LUSE volume.

Usage Restrictions If an LDEV is placed in cache, do not use it for BC/Continuous Access XP quickrestore operations or Auto LUN XP migration. These operations may swap theinternal locations of the primary and secondary volumes and cause a loss ofdata integrity.

You cannot change a Cache LUN XP extent after it is configured. To change thespecification, you must reset (release) the Cache LUN XP extent, and thenre-allocate (set) the Cache LUN XP extent.

CVS Automatic Resets In the following cases, a Cache LUN XP cache extent is deleted ( resetor released)automatically:

If a fixed volume, part or all of which is assigned to Cache LUN XP, isconverted into free space by the CVS Volume to Space function.

If a custom volume, part or all of which is assigned to Cache LUN XP, isconverted into free space using the CVS Volume to Space function.

If an LDEV (or VDEV) containing fixed and custom volumes assigned to CacheLUN XP is initialized by the CVS Volume Initialize function.


11/20


While destaging to disk, read requests to the same block are delayed until the disk operation iscompleted.

Priority mode generates write traffic to disk, whereas bind mode does not.

General cache capacity

In addition to the Cache LUN XP cache, you should set the general cache capacity according to thenumber of areas set in priority mode. This prevents a reduction in general cache performance.

If the general cache is overloaded (having very little cache space), this can result in a wait for free cache

space. This may degrade access to the general cache. If you set up to 512 areas in Cache LUN XP, set 512 MB x 2 (1024 MB) of standard cache.

If you set 513-1024 areas in Cache LUN XP, set 1024 MB x 2 (2048 MB) of standard cache.

For OPEN-V, one slot is 66 KB, which requires 4 cache segments (16.5 KB/segment). For example,16 slots require 1,056 KB of reserved cache.

For other than OPEN-V, one slot is 49.5 KB, which requires 3 cache segments. For example, 16 slotsrequire 792 KB of reserved cache.

Bind modeBind mode keeps both read and write data in cache, eliminating disk traffic (100% read/write hits). Alldata stays in cache until the extent is removed. The data stored in the Cache LUN XP cache is duplexed for

data protection, which requires additional Cache LUN XP cache capacity. If AC power is lost, data ismaintained in cache for up to 48 hours, using battery power.

Bind mode details

All reads following the initial read to a block will result in cache hits.

Duplicated write blocks are stored in cache and are never evicted.

All read or write blocks stay resident in cache until the extent is deleted.

Bind mode requires more cache because duplicated write blocks are not destaged to disk.

Bind mode and RAID groups

For RAID-5 parity groups, a Cache LUN XP extent in bind mode requires a cache capacity three timeslarger than the user data.


For other than OPEN-V, one slot is 49.5 KB, which requires 9 cache segments. For example, 16 slotsrequire 2,376 KB of reserved cache.

For RAID-1 parity groups, a Cache LUN XP extent in bind mode requires a cache capacity twice as largeas user data.


For other than OPEN-V, one slot is 49.5 KB, which requires 6 cache segments. For example, 16 slotsrequire 1,584 KB of reserved cache.

If you want to change a RAID-1 or RAID-5 parity groups mode from priority mode to bind mode, reset andre-allocate the affected Cache LUN XP extent. When you re-allocate, specify the greater capacity neededfor bind mode.

Pre-stagingAs mentioned before, data assigned to a Cache LUN XP cache extent becomes resident (staged) incache after it is first accessed by the host. Then, the host finds the data in cache for the second andsubsequent accesses. The pre-staging function puts data in cache before the first read. Therefore,pre-staging allows the host to find data in cache on the first access.

Specify pre-staging when you set up the cache extent. You can use this function with either priority or bindmode.


12/20


You cannot change a Cache LUN XP extent after it is configured. To change the specification, you mustreset (release) the Cache LUN XP extent, and then re-allocate (set) the Cache LUN XP extent.

Starting Cache LUN XP1. Click Cache LUN in the left pane. The Cache LUN pane appears.

Figure 2 Cache LUN pane

Cache LUN paneThis pane lists the following items:

Prestaging check box

Select or clear this check box to enable or disable the pre-staging function:

If you select this check box, set the Prestaging Mode to Yes and clickApply. A non-pre-stagingoperation will be performed and then a pre-staging operation will be performed.

If you clear this check box and then clickApply, a non-pre-staging operation will be performed, but apre-staging operation will not be performed. If you select this check box later and then clickApply, onlya pre-staging operation will be performed.

When a pre-staging operation is in progress, the text Prestaging operation in progress is shown at thebottom of the Cache LUN pane. The progress is displayed in percentage.

The Prestaging check box is enabled in Modify mode and is selected by default. However, the Prestagingcheck box is disabled in either of the following conditions:

No cache

Prestaging mode is set to No for each cache

LDEV tree

The LDEV tree displays the CU number (for example, CU 00) and LDEV number (for example, LDEV 00)available for Cache LUN XP operations in a tree. The tree uses the following icons to show the settings:

Table 4 Cache LUN XP icons

Icon Description

Indicates an LDEV for which Cache LUN XP is not set.

Indicates an LDEV for which Cache LUN XP is set.

Indicates a LUSE volume (two or more LDEVs) for which Cache LUN XP is not set.


13/20


The LDEV tree does not show Auto LUN-reserved volumes because they cannot be used in Cache LUN XPoperations.

LDEV table

Information about the LDEV selected in the tree appears on a single line in the upper-right portion of thepane. It includes LDEV number, emulation type, capacity, and RAID level.

The LDEVs capacity is shown in MB for open systems, or cylinders and tracks for mainframe systems. Thetable shows the cache settings for the LDEV selected in the tree and contains the following columns:

LBA(open systems only): Displays the logical block starting and ending addresses. CC HH (mainframe systems only): Displays the cylinder and head starting and ending addresses.

Capacity: Displays the capacity of the cache extent in megabytes for open systems. Displays thecapacity of the cache extent in cylinders and tracks for mainframe systems.

Mode: Displays the mode of the cache extent. PRIO indicates priority mode, BIND indicates bind mode,and - indicates that the LDEV is not assigned to the cache.

Prestage: If this is blank, then pre-staging is not set. ON indicates that pre-staging is set.

Cache LUN pie chart

The text above the pie chart lists the used cache and the amount of free space left in cache.

In the pie chart, pink indicates the amount of cache available, blue shows cache used, and yellow shows

the size of the specified cache extent.

Cache settings section

Sets the mode and area for data that will reside in the Cache LUN XP cache. Also displays the settings foran existing cache extent. This area contains the following:

Cache LUN Type: Select the Cache LUN XP mode by clicking either Bind or Prio.

Prestaging Mode: Select the Prestaging check box (located above the LDEV tree) to perform thepre-staging operation, and then clickApply. ClickYes if pre-staging is enabled. Click No if pre-stagingis disabled.

From: The starting address for data that will reside in the cache. This is expressed as a logical blockaddress for open systems and as a cylinder and head address for mainframe systems.

To: The ending address for data that will reside in the cache. This is expressed as a logical blockaddress for open systems and as a cylinder and head address for mainframe systems.

Select All Area check box: If you select this check box, all data areas in the selected LDEV will be set toCache LUN XP cache.

This check box can be selected if no data areas in the selected LDEV are set to Cache LUN XP cache.This check box cannot be selected and is grayed out if some data areas in the selected LDEV are set toCache LUN XP cache. If you select the Select All Area check box, nothing will be set to the startingaddress and the ending address, and the From and To fields remain empty.

Possible Cache LUN Size: Displays the size you can set. Bind displays the size you should set for bindmode and Prio displays the size you should set for priority mode.

Multi Set / Release check box: Selecting this check box and then clicking Set displays the Multi Set

pane, which you can use to make Cache LUN XP settings on more than one LDEV. Selecting this checkbox and then clicking Release displays the Multi Release pane, which you can use to cancel CacheLUN XP settings on more than one LDEV.

Data that will reside in the Cache LUN XP cache is specified by the starting address in the From fieldand the ending address in the To field. When the Select All Area check box is selected, all data areasof the selected LDEVs will be set for the Cache LUN XP.

If you cancel the settings, all the settings specified for the LDEV will be canceled.

The Multi Set / Release check box does not select and cancel an individual Cache LUN XP data areaspecified for the LDEV. You must use the Release button to cancel an individual Cache LUN XP dataarea.


14/20


Buttons

Set: Creates a cache extent.

Release: Deletes a cache extent.

Apply: Applies the parameters to the disk array. You can then set or release other cache extents.

Cancel: Cancels the operation.

Setting (creating) a cache extent

1. In the LDEV tree of the Cache LUN pane, click the CU:LDEV number of the LDEV you want to put incache.

The LDEV table displays Cache LUN XP information for the LDEV you selected.

2. Select an area to be made resident in the Cache LUN XP cache from one of those marked - in theMode column. The Set button is enabled. The From and To boxes display the selected areas values.

3. Click Bind or Prio to indicate the mode.

4. ClickYes or No to indicate whether to set pre-staging.

5. Complete one of the following steps:

To place all data on an LDEV into cache, go to step 6.

To place specific data from an LDEV into cache, go to step 7.

To place all data on multiple LDEVs into cache, go to step 8.

To place specific data from multiple LDEVs into cache, go to step 9.

6. To place all data on an LDEV into cache:

a. Select the Select All Area check box.

b. Clear the Multi Set / Release check box.

c. Click Set. A confirmation dialog box appears.

d. Click OKto continue. The new settings are shown in blue on the Cache LUN pane. To canceloperations, click Cancel. Go to step 10.

7. To place specific data from an LDEV into cache:

a. If the Select All Area check box is grayed out, go to the next step. If the Select All Area check box is

activated, clear the Select All Area check box.b. Enter the starting and ending addresses (LBAs or CC HHs) of the area to be made resident in thecache.

For open systems, Cache LUN XP identifies a logical area in units of 128 blocks for OPEN-V, and96 blocks for other than OPEN-V. For OPEN-V, if you have entered 1 as the starting logical blockaddress and a value less than 128 as the ending logical block address, Cache LUN XPautomatically changes the ending block address to 128. For other than OPEN-V, if you haveentered 1 as the starting logical block address and a value less than 96 as the ending logical blockaddress, Cache LUN XP automatically changes the ending block address to 96.

c. Clear the Multi Set / Release check box.

d. Click Set. A confirmation dialog box appears.

e. Click OKto continue. The new settings are shown in blue on the Cache LUN pane. To canceloperations, click Cancel. Go to step 10.

8. To place all data on multiple LDEVs into cache:

a. Select the Select All Area check box.

b. Select the Multi Set / Release check box.

c. Click Set. A confirmation dialog box appears.


15/20


d. Click OKto continue. The Multi Set pane appears.

Figure 3 Multi Set pane

e. In the CU drop-down list, click the CU.f. In the table, click more than one LDEV and then click Set. The Multi Set pane closes and the new

settings are shown in blue on the Cache LUN pane. To cancel operations, click Cancel. Go tostep 10.

9. To place specific data from multiple LDEVs into cache:

a. If the Select All Area check box is grayed out, go to the next step. If the Select All Area check box isactivated, clear the Select All Area check box.

b. Enter the starting and ending addresses (LBAs or CC HHs) of the area to be made resident in thecache.

For open systems, Cache LUN XP identifies a logical area in units of 128 blocks for OPEN-V, and96 blocks for other than OPEN-V. For OPEN-V, if you have entered 1 as the starting logical block

address and a value less than 128 as the ending logical block address, Cache LUN XPautomatically changes the ending block address to 128. For other than OPEN-V, if you haveentered 1 as the starting logical block address and a value less than 96 as the ending logical blockaddress, Cache LUN XP automatically changes the ending block address to 96.

c. Select the Multi Set / Release check box.

d. Click Set. A confirmation dialog box appears.

e. Click OKto continue. The Multi Set pane appears.

f. In the CU drop-down list, click the CU.

g. In the table, click more than one LDEV and then click Set. The Multi Set pane closes and the newsettings are shown in blue on the Cache LUN pane. To cancel operations, click Cancel. Go tostep 10.

10.To make data in other volumes reside in the Cache LUN XP cache, repeat the previous steps.

NOTE: You cannot use the Release button to delete the set data until you clickApply or Cancel.

11.To enable the pre-staging function, select the Prestaging check box. To disable the pre-staging function,clear the Prestaging check box.

12.If the settings are correct, clickApply. A confirmation dialog box appears.

13.Click OKto confirm. The Cache LUN XP operation begins. If prestaging was selected, the prestagingoperation will occur next. When the operation has been completed, a confirmation dialog boxappears.

14.Click OK.


16/20


Releasing (removing) a cache extent1. In the LDEV tree of the Cache LUN pane, click the CU:LDEV number of the LDEV you want to remove

from cache. The LDEV table displays Cache LUN XP information about the LDEV you selected.

2. Select an extent to be removed from the Cache LUN XP cache. The Release button is enabled.

3. Complete one of the following steps:

To remove specific data from cache, go to step 4.

To remove all data from cache, go to step 5.

4. To remove specific data from cache:a. Click Release. A confirmation dialog box appears.

b. Click OKto continue. The new settings are shown in blue on the Cache LUN pane. To canceloperations, click Cancel. Go to step 6.

5. To remove all data from cache

a. Select the Multi Set / Release check box.

b. Click Release. A confirmation dialog box appears.

c. Click OKto continue. The Multi Release window appears.

Figure 4 Multi Release pane

d. In the CU box, click the CU.

e. In the table, click more than one LDEV and then click Release. The Multi Release pane closes andthe new settings are shown in blue on the Cache LUN pane. To cancel operations, click Cancel. Goto step 6.

6. To remove cache data for another CU:LDEV, repeat the previous steps.

7. If the deletions are correct, clickApply. A confirmation dialog box appears.

8. Click OKto confirm. The Cache LUN XP operation begins. If prestaging was selected, the prestagingoperation will occur next. When the operation has been completed, a confirmation dialog boxappears.

9. Click OK.


17/20


Changing an extents mode and pre-stagingYou cannot directly change a cache extents mode or pre-staging settings. You must delete the extent andreconfigure it with new settings.

1. Select and release (remove) the extent in the Cache LUN XP cache.

2. Remake the extent with the new mode and pre-staging settings.


18/20



19/20


Index

Aaudience, documentation5available space13

Bbattery backup11bind mode11buttons14

Ccache extents11

about9creating14removing16size requirements10

Cache LUN pane12conventions

document6text symbols6

creating cache extents14CU number12custom volumes9customer support6

Ddocument

conventions6prerequisites5related documentation5

Eemulation types supported9extents, cache11

about9creating14removing16size requirements10

Ffirmware versions5

free space13

Hhelp, obtaining6, 7HP

storage web site7Subscribers choice web site6technical support6

LLDEV table13LDEV tree12

logical blocks10

Mmemory requirements9modes

settings17types of10

Ooperations9

Ppie chart13prerequisites5pre-staging

about11enabling or disabling12settings17

priority mode10

RRAID parity groups11related documentation5releasing cache extents16removing cache extents16restrictions10

Ssetting cache extents14settings13size, cache free space13starting Cache LUN XP12Subscribers choice, HP6supported volumes9symbols in text6

Ttasks9technical support, HP6text symbols6

Vvolumes supported9

Wweb sites

HP documentation5HP storage7HP Subscribers choice6


20/20

hp_cachelun_xp1024ug rootsan technologies pvt ltd

Documents