HP 3PAR StoreServ 7400 4-node Administrator's Manual

HP 3PAR StoreServ 7400 4-node is a high-performance, scalable storage system designed for demanding enterprise environments. It offers a range of features to meet the needs of mission-critical applications, including:

High availability and data protection: with its redundant components and advanced data protection features, the HP 3PAR StoreServ 7400 4-node ensures that your data is always available and protected.
Scalability and performance: the HP 3PAR StoreServ 7400 4-node can be scaled to meet the growing needs of your business, and its high-performance design ensures that your applications will always have the resources they need.
Easy management: the HP 3PAR StoreServ 7400 4-node is easy to manage, with a simple and intuitive web-based interface. This makes it easy to provision storage, manage users, and monitor the system's performance.

PDF

Document

HP 3PAR Command Line Interface

Administrator’s Manual

HP 3PAR OS 3.1.2

Abstract

This manual is for all levels of system and storage administrators. This guide provides instructions for installing the HP 3PAR

CLI and using the CLI to configure and manage HP 3PAR storage systems.

HP Part Number: QR482-96525

Published: September 2013

Edition: 1

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.

Acknowledgements

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Java, Oracle, and Oracle Solaris are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Warranty

WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website: http://www.hp.com/go/storagewarranty

1 Installing the HP 3PAR Command Line Interface............................................12

About the HP 3PAR Command Line Interface..............................................................................12

Supported Platforms................................................................................................................12

System Requirements...............................................................................................................12

Disk Space Requirements.........................................................................................................12

Installation.............................................................................................................................12

Before Installation..............................................................................................................13

Graphical Installation on Windows......................................................................................13

Command-Line Installation on Solaris and Linux.....................................................................13

Setting the Path to the CLI on Solaris and Linux......................................................................13

Troubleshooting the Installation.................................................................................................14

Removing the HP 3PAR CLI......................................................................................................14

On Windows....................................................................................................................14

On Solaris and Linux..........................................................................................................14

Scripting Considerations..........................................................................................................14

2 Managing User Accounts and Connections..................................................16

Learning About User Accounts..................................................................................................16

Default User Accounts.........................................................................................................17

Authenticating and Authorizing CLI Users..............................................................................17

Viewing User Roles and Rights..................................................................................................17

Creating Users.......................................................................................................................18

Viewing Users........................................................................................................................19

Removing Users......................................................................................................................20

Adding Users to a Domain......................................................................................................20

Removing Users From a Domain...............................................................................................20

Setting a User’s Default Domain...............................................................................................20

Removing a User’s Default Domain...........................................................................................20

Setting a User’s Current Domain...............................................................................................21

Removing a User’s Current Domain...........................................................................................21

Viewing User Connections.......................................................................................................21

Removing User Connections.....................................................................................................21

Configuring LDAP Connections.................................................................................................21

Active Directory LDAP Configuration with SASL Binding...........................................................22

Configuring Connection Parameters.................................................................................23

Configuring Binding Parameters......................................................................................24

Configuring Account Location Parameters.........................................................................24

Configuring Group-to-Role Mapping Parameters................................................................26

Active Directory LDAP Configuration with Simple Binding Over SSL..........................................27

Configuring Connection Parameters.................................................................................28

Configuring Binding Parameters......................................................................................29

Configuring the CA Certificate........................................................................................29

Configuring Account Location Parameters.........................................................................30

Configuring Group-To-Role Mapping Parameters...............................................................32

OpenLDAP Configuration with Simple Binding Over SSL.........................................................33

Configuring Connection Parameters.................................................................................34

Configuring Binding Parameters......................................................................................34

Configuring Group Location Parameters...........................................................................35

Configuring Group-To-Role Mapping Parameters...............................................................35

Configuring LDAP Connections on Systems Using Domains...........................................................38

Contents 3

3 Running the HP 3PAR Command Line Interface.............................................41

Global Options and Environment Variables................................................................................41

General Control and Help Commands..................................................................................43

Commands with Column Help.............................................................................................43

Using SSL.........................................................................................................................44

Setting the TPDSOCKSSL Environment Variable on Solaris and Linux....................................44

Setting the TPDSOCKSSL Environment Variable on Windows...............................................44

Using the -sockssl Option...............................................................................................44

Setting the CLI Client Network Port.......................................................................................44

Setting the TPDSYSNAME Environment Variable.....................................................................45

Setting the TPDSYSNAME Environment Variable on Solaris and Linux...................................45

Setting the TPDSYSNAME Environment Variable on Windows.............................................45

Using the -sys Option.....................................................................................................45

Using the System Name.................................................................................................45

Setting Your Name and Password........................................................................................46

Using the setpassword Command....................................................................................46

Setting the TPDPWFILE Environment Variable....................................................................46

Using the -pwf Option....................................................................................................46

Using the -password Option............................................................................................47

Setting a Password for Multiple HP 3PAR Storage Arrays....................................................47

Caching Client Bytecode.....................................................................................................47

Setting the TPDCACHEDIR Environment Variable on Solaris and Linux..................................47

Setting the TPDCACHEDIR Environment Variable on Windows............................................47

Startup Files......................................................................................................................48

Setting the TPDSTARTFILE Environment Variable on Solaris and Linux....................................48

Setting the TPDSTARTFILE Environment Variable on Windows..............................................48

Comma Separated Values...................................................................................................48

Setting the TPDCSVTABLE Environment Variable on Solaris and Linux...................................49

Setting the TPDCSVTABLE Environment Variable on Windows..............................................49

Using the -csvtable Option..............................................................................................49

Listing Domains.................................................................................................................49

Setting the TPDLISTDOM Environment Variable on Solaris and Linux.....................................50

Setting the TPDLISTDOM Environment Variable on Windows...............................................50

Using the -listdom Option...............................................................................................50

Table Headers and Totals...................................................................................................50

Setting the Environment Variable on Solaris and Linux........................................................50

Setting the Environment Variable on Windows..................................................................51

Using the -nohdtot Option..............................................................................................51

Using the -hafter Option.................................................................................................51

Forcing Commands............................................................................................................51

Setting the TPDFORCE Environment Variable on Solaris and Linux........................................51

Setting the TPDFORCE Environment Variable on Windows..................................................51

Stand-alone Commands..........................................................................................................52

SSH......................................................................................................................................52

Benefits of Using SSH.........................................................................................................52

CLI User Name Restrictions Using SSH..................................................................................53

New Users...................................................................................................................53

Existing Users...............................................................................................................53

Accessing the CLI Using SSH...............................................................................................53

CLI Scripting Through SSH..................................................................................................54

4 Managing HP 3PAR Virtual Domains..........................................................58

Overview..............................................................................................................................58

Default Domains.....................................................................................................................58

Creating a Domain.................................................................................................................58

4 Contents

Viewing Domains...................................................................................................................59

Modifying a Domain...............................................................................................................59

Changing a Domain Name.................................................................................................59

Adding Comments to a Domain...........................................................................................59

Removing a Domain...............................................................................................................59

Managing Domain Objects.....................................................................................................60

Moving Domain Objects to Another Domain.........................................................................60

Removing the Domain Association from a Domain Object.......................................................60

Managing Virtual Domain Autonomic Groups............................................................................60

Creating Virtual Domain Sets..............................................................................................61

Adding Virtual Domains to Virtual Domain Sets.....................................................................61

Modifying Virtual Domain Sets............................................................................................61

Removing Virtual Domain Sets.............................................................................................61

Viewing Virtual Domain Sets...............................................................................................61

5 Managing Ports and Hosts.........................................................................63

Overview..............................................................................................................................63

Modifying Port Parameters.......................................................................................................63

FC Port Settings.................................................................................................................64

iSCSI Port Settings..............................................................................................................65

Port Target, Initiator, and Peer Modes........................................................................................65

Active and Inactive Hosts.........................................................................................................66

Managing Hosts.....................................................................................................................66

Host Management CLI Commands.......................................................................................66

Creating Hosts.......................................................................................................................67

Creating a Host with a Fibre Channel Path............................................................................67

Creating a Host with an iSCSI Path......................................................................................67

Creating a Host without Assigning a Path..............................................................................67

Modifying Hosts.....................................................................................................................68

Changing a Host Name.....................................................................................................68

Adding Fibre Channel Path WWNs.....................................................................................68

Adding iSCSI Path iSCSI Names..........................................................................................68

Removing Fibre Channel Path WWNs..................................................................................68

Removing iSCSI Path iSCSI Names.......................................................................................69

Configuring iSCSI CHAP Authentication Information...............................................................69

Removing iSCSI CHAP Authentication Information..................................................................69

Moving, Removing, and Disconnecting Hosts..............................................................................69

Removing Host Paths...............................................................................................................70

Managing Host Autonomic Groups...........................................................................................71

Creating Host Sets.............................................................................................................71

Adding Hosts to Host Sets...................................................................................................71

Modifying Host Sets...........................................................................................................71

Removing Host Sets............................................................................................................71

Managing Host Personas.........................................................................................................72

The Host Explorer Software Agent.............................................................................................73

Hosts and Virtual Domains.......................................................................................................73

Creating a Domain-Specific Host.........................................................................................74

Modifying a Domain-Specific Host.......................................................................................74

Changing a Host Domain...................................................................................................74

Using Persistent Ports for Nondisruptive Online Software Upgrades...............................................74

6 Managing CPGs and Virtual Volumes.........................................................78

Overview..............................................................................................................................78

Common Provisioning Groups..................................................................................................78

Growth Increment Considerations for Common Provisioning Groups..........................................78

System Guidelines for Creating Common Provisioning Groups.................................................79

Contents 5

Common Provisioning Group CLI Commands.............................................................................79

Creating a Common Provisioning Group....................................................................................80

Modifying a Common Provisioning Group.................................................................................80

Setting Snapshot Space Usage Warnings.............................................................................80

Setting a Common Provisioning Group’s Autogrow Size..........................................................80

Consolidating Common Provisioning Group Space.................................................................81

Removing a Common Provisioning Group.............................................................................81

Virtual Volume Types...............................................................................................................81

Fully Provisioned Virtual Volumes..........................................................................................82

Thinly Provisioned Virtual Volumes........................................................................................82

Virtual Volume CLI Commands.................................................................................................82

Creating Virtual Volumes.........................................................................................................83

Creating Fully Provisioned Virtual Volumes.............................................................................83

Creating Thinly Provisioned Virtual Volumes...........................................................................83

Modifying Virtual Volumes.......................................................................................................84

Growing Virtual Volumes.........................................................................................................84

Converting Virtual Volumes Online............................................................................................84

Converting Fully Provisioned Virtual Volumes to Thinly Provisioned Virtual Volumes......................85

Converting Thinly Provisioned Virtual Volumes to Fully Provisioned Virtual Volumes......................85

Reducing Volume Size with HP 3PAR Thin Conversion Software....................................................85

Manually Converting a Fully Provisioned Virtual Volume to a Thinly Provisioned Virtual Volume....86

Reducing Volume Size with HP 3PAR Thin Persistence Software.....................................................86

Managing Virtual Volume Autonomic Groups.............................................................................87

Creating Virtual Volume Sets...............................................................................................87

Adding Virtual Volumes to Virtual Volume Sets.......................................................................87

Modifying Virtual Volume Sets.............................................................................................87

Removing Virtual Volume Sets..............................................................................................87

Freeing Virtual Volume Snapshot Space.....................................................................................88

Setting Expiration Times for Virtual Volumes...............................................................................88

Setting Retention Times for Virtual Volumes.................................................................................88

Removing Virtual Volumes........................................................................................................89

Validating and Repairing Virtual Volumes..................................................................................90

Exporting Virtual Volumes........................................................................................................90

Creating VLUN Templates...................................................................................................90

Creating a Host Sees or Host Set VLUN Template..............................................................90

Creating a Port Presents VLUN Template...........................................................................91

Creating a Matched Set VLUN Template..........................................................................91

Unexporting Virtual Volumes....................................................................................................91

Removing a Host Sees or Host Set VLUN Template.................................................................91

Removing a Port Presents VLUN Template..............................................................................92

Removing a Matched Set VLUN Template..............................................................................92

Virtual Domains, CPGs, and Virtual Volumes..............................................................................92

Creating a Common Provisioning Group in a Domain............................................................92

Creating Virtual Volumes in a Virtual Domain........................................................................93

Modifying Virtual Volumes in Domains.................................................................................93

Growing Virtual Volumes in Domains....................................................................................94

Freeing Virtual Volume Snapshot Space in Domains...............................................................94

Exporting Virtual Volumes in Domains..................................................................................94

Creating VLUN Templates in the All Domain.....................................................................94

Creating VLUN Templates in a Specific Domain................................................................94

Moving a Common Provisioning Group to a Domain..............................................................94

7 Managing Virtual Volume Copies...............................................................95

Virtual Copies........................................................................................................................95

Creating a Virtual Copy......................................................................................................95

6 Contents

Promoting a Virtual Copy....................................................................................................96

Modifying a Virtual Copy...................................................................................................96

Removing a Virtual Copy....................................................................................................97

Creating a Group of Virtual Copies......................................................................................97

Physical Copies......................................................................................................................97

Creating an Offline Physical Copy.......................................................................................98

Creating an Online Physical Copy.......................................................................................98

Creating a Group of Physical Copies....................................................................................99

Resynchronizing a Physical Copy.........................................................................................99

Resynchronizing a Group of Physical Copies.....................................................................99

Promoting a Physical Copy................................................................................................100

Creating an Online Copy.................................................................................................100

Snapshots and Domains........................................................................................................100

Moving Snapshots...........................................................................................................101

8 Creating and Applying Templates.............................................................102

Overview............................................................................................................................102

Creating Templates...............................................................................................................102

Applying Templates..............................................................................................................102

Creating Virtual Volumes and Logical Disks Using a Template................................................103

Creating a Common Provisioning Group Using a Template....................................................103

Modifying Templates.............................................................................................................103

Viewing Template Parameters............................................................................................103

Adding and Replacing Template Parameters........................................................................103

Removing Template Parameters..........................................................................................104

Removing Templates.........................................................................................................104

9 Monitoring System and Physical Disk Capacity...........................................105

Overview............................................................................................................................105

System Capacity...................................................................................................................105

Determining Total System Capacity.....................................................................................105

Determining System Capacity by Physical Disk Type.............................................................106

Physical Disk Capacity..........................................................................................................106

Determining Total Physical Disk Capacity............................................................................106

Determining Physical Disk Capacity by Disk Type.................................................................107

Determining the Capacity of a Specific Physical Disk............................................................107

Spare Chunklets...................................................................................................................107

Viewing Spare Chunklets..................................................................................................108

Logical Disks and Chunklet Initialization..............................................................................109

Recovering Failed RAID Sets..................................................................................................109

Viewing Hardware Inventory..................................................................................................109

10 Data Encryption....................................................................................111

Supported Configurations......................................................................................................112

Data Encryption Licensing......................................................................................................112

Restrictions...........................................................................................................................113

Using Self-encrypting Disks....................................................................................................113

Taking Ownership............................................................................................................113

Using the controlencryption command................................................................................114

Enabling Encryption....................................................................................................114

Backing up the Authentication Key File...........................................................................115

Restoring the Key File...................................................................................................115

Rekeying the Authentication Key....................................................................................115

Showing Data Encryption Status....................................................................................115

Replacing a Failed Disk Drive............................................................................................116

Upgrading an SED with New Firmware..............................................................................116

Contents 7

Dismissing an Existing SED...............................................................................................117

Data Encryption Commands..............................................................................................117

11 Managing Events and Alerts...................................................................118

Overview............................................................................................................................118

Checking the Status of a System.............................................................................................118

Monitoring and Managing Alerts...........................................................................................118

Viewing Alerts.................................................................................................................118

Setting an Alert State........................................................................................................118

Removing an Alert...........................................................................................................118

Setting System Alerts.............................................................................................................118

Setting the Raw Space Threshold Alert................................................................................119

Monitoring and Managing the Event Log.................................................................................119

Viewing the Event Log.......................................................................................................120

Removing the Event Log....................................................................................................120

Stopped Logical Disks and Missing Physical Disks.....................................................................120

Preserved Data................................................................................................................120

12 Viewing Statistics and Histograms...........................................................121

Overview............................................................................................................................121

Viewing Statistics..................................................................................................................121

Viewing Statistics for Physical Disks....................................................................................121

Viewing Port Statistics.......................................................................................................121

Viewing VLUN Statistics....................................................................................................122

Viewing Virtual Volume Statistics........................................................................................122

Viewing Statistics for Data Cache Memory..........................................................................122

Viewing Statistics for CPU Usage.......................................................................................122

Viewing Statistical Reports Using the On-node System Reporter..............................................123

Viewing Statistical Report for Region I/O Density.................................................................123

Viewing Statistical Reports for Used Capacity (Space Reports)...............................................123

Viewing Statistical Reports for Performance..........................................................................123

Viewing Statistical Histogram Reports for Performance..........................................................124

Viewing Histograms..............................................................................................................124

Viewing Histograms for Chunklets......................................................................................124

Viewing Histograms for Logical Disks..................................................................................124

Viewing Histograms for Physical Disks................................................................................124

Viewing Histograms for Ports.............................................................................................125

Viewing Histograms for VLUNs..........................................................................................125

Viewing Histograms for Virtual Volumes..............................................................................125

13 Managing Tasks...................................................................................126

Overview............................................................................................................................126

Task Manager......................................................................................................................126

Task IDs..........................................................................................................................126

Task Manager Commands................................................................................................126

Starting a Task................................................................................................................127

Displaying Task Information...............................................................................................127

Setting the Priority of a Running Task..................................................................................128

Waiting for a Task...........................................................................................................129

Removing a Task..............................................................................................................130

Canceling a Task.............................................................................................................130

Task Types...........................................................................................................................130

background_command.....................................................................................................132

compact_cpg..................................................................................................................132

compact_lds....................................................................................................................132

promote_sv.....................................................................................................................132

8 Contents

remote_copy_sync............................................................................................................132

scheduled_task................................................................................................................133

snapspace_accounting.....................................................................................................133

startao............................................................................................................................133

system_task.....................................................................................................................134

tune_vv...........................................................................................................................134

tune_vv_restart................................................................................................................134

tunevv_rollback................................................................................................................135

tune_sys..........................................................................................................................136

tune_sd..........................................................................................................................136

vv_copy..........................................................................................................................137

System Scheduler..................................................................................................................137

System Scheduler Commands............................................................................................137

Displaying Scheduled Tasks...............................................................................................138

Scheduling Tasks.............................................................................................................138

Modifying a Scheduled Task.............................................................................................139

Suspending and Resuming Scheduled Tasks........................................................................139

Removing Scheduled Tasks................................................................................................139

14 Adaptive Optimization...........................................................................140

Adaptive Optimization Conversion..........................................................................................141

Creating an Adaptive Optimization Configuration.....................................................................142

Displaying an Adaptive Optimization Setting...........................................................................144

Modifying an Adaptive Optimization Configuration..................................................................144

Removing an Adaptive Optimization Configuration...................................................................146

15 HP Priority Optimization.........................................................................147

Requirements.......................................................................................................................147

Virtual Volume Sets...............................................................................................................147

Applying Quality of Service Rules...........................................................................................151

Mode of Operation..........................................................................................................152

QoS Rule Minimum and Maximum.....................................................................................152

QoS Rule Actions.............................................................................................................153

Overlapping QoS rules.....................................................................................................153

Minimum QoS Settings.....................................................................................................153

QoS on Copied Volumes..................................................................................................153

QoS Metrics....................................................................................................................154

Using HP 3PAR Priority Optimization.......................................................................................154

Creating a New QoS Rule................................................................................................154

Creating a New QoS Rule with the HP 3PAR CLI.............................................................154

Creating a New QoS Rule with the HP 3PAR MC............................................................155

Viewing a QoS Rule.........................................................................................................158

Modifying a QoS Rule......................................................................................................158

Removing a QoS Rule.......................................................................................................159

Managing QoS Rules.......................................................................................................160

Assembling VVs into VVsets..........................................................................................160

Determining the Values for IOPS and Bandwidth for a System...........................................160

Handling Tier-1 Applications.........................................................................................161

Implementing the System Rule.......................................................................................161

Overprovisioning the System.........................................................................................161

QoS Influence on the Host Side.....................................................................................161

Maximum Number of QoS Rules per VV........................................................................162

QoS on a Subset of VVset Volumes................................................................................162

Application Interoperability..........................................................................................162

Databases.............................................................................................................162

Microsoft Exchange................................................................................................162

Contents 9

Virtualization Software.................................................................................................163

Reporting...................................................................................................................164

Event Management......................................................................................................166

16 Using the HP 3PAR SNMP Infrastructure...................................................167

Overview............................................................................................................................167

The HP 3PAR SNMP Agent....................................................................................................167

Locating the HP 3PAR MIB................................................................................................167

alertNotify Traps..............................................................................................................167

Registering an SNMP Manager..............................................................................................167

Viewing Registered Managers...........................................................................................168

Removing a Manager.......................................................................................................168

Agent Community Strings..................................................................................................168

Testing SNMP Managers..................................................................................................168

Creating SNMPv3 Users........................................................................................................168

Viewing SNMPv3 Users.........................................................................................................169

Removing SNMPv3 Users......................................................................................................169

Modifying SNMP Versions.....................................................................................................169

17 Using mySnapshot................................................................................170

Overview............................................................................................................................170

About mySnapshot................................................................................................................170

Setting Administrative Rights...................................................................................................170

Replacing Virtual Volume Snapshots........................................................................................170

Replacing a Read-Only Snapshot.......................................................................................171

Replacing a Read-Write Snapshot......................................................................................171

18 Performance Tuning...............................................................................173

Analyzing and Tuning a System..............................................................................................173

Displaying Virtual Volume Space Distribution............................................................................174

Tuning and Modifying Virtual Volumes....................................................................................174

Changing Virtual Volume Layouts.......................................................................................174

Thinly-Provisioned Virtual Volumes.................................................................................175

Fully-Provisioned Virtual Volumes...................................................................................175

Changing Virtual Volume RAID Levels.................................................................................175

Thinly-Provisioned Virtual Volumes.................................................................................175

Fully-Provisioned Virtual Volumes...................................................................................175

Changing Virtual Volume Fault-Tolerance Levels....................................................................176

Thinly-Provisioned Virtual Volumes.................................................................................176

Fully-Provisioned Virtual Volumes...................................................................................176

Changing Virtual Volume Parameters..................................................................................176

Thinly-Provisioned Virtual Volumes.................................................................................176

Fully-Provisioned Virtual Volumes...................................................................................176

Troubleshooting Modifying Virtual Volumes..............................................................................177

Rolling Back a Volume Modification Task............................................................................177

Restarting a Volume Modification Task................................................................................177

Tuning Physical Disks............................................................................................................177

Compacting Logical Disks......................................................................................................178

Compacting Common Provisioning Groups..............................................................................179

19 Support and Other Resources.................................................................180

Contacting HP......................................................................................................................180

HP 3PAR documentation........................................................................................................180

Typographic conventions.......................................................................................................183

HP 3PAR branding information...............................................................................................183

10 Contents

20 Documentation feedback.......................................................................184

A Mapping Roles and Rights.......................................................................185

3PAR AO Role......................................................................................................................185

3PAR RM Role......................................................................................................................185

Basic Edit Role.....................................................................................................................186

Browse Role.........................................................................................................................188

Create Role..........................................................................................................................188

Edit Role..............................................................................................................................189

Service Role.........................................................................................................................191

Super Role...........................................................................................................................192

B Mapping Rights and CLI Commands.........................................................197

Mapping Rights and CLI Commands.......................................................................................197

Index.......................................................................................................201

Contents 11

1 Installing the HP 3PAR Command Line Interface

The purpose of this chapter is to provide instructions for installing and uninstalling the HP 3PAR

Command Line Interface.

About the HP 3PAR Command Line Interface

Use the HP 3PAR Command Line Interface (CLI) to monitor, manage, and configure HP 3PAR storage systems. See the HP 3PAR CLI installation readme file on the HP 3PAR CLI and SNMP CD.

All platforms use the same CD, but the installation files are different for each of the supported platforms.

Supported Platforms

The HP 3PAR CLI is supported on HP-UX (with HP 3PAR OS 3.1.2 and later), Linux, Oracle Solaris

(Solaris), and Microsoft Windows operating systems. For a list of supported versions of each operating system, see the Single Point of Connectivity Knowledge (SPOCK) website http:// www.hp.com/storage/spock .

NOTE: Update your operating system with all required and recommended patches or service packs before installing the HP 3PAR CLI.

System Requirements

The HP 3PAR CLI uses port number 5783 for secure communications and port 5782 for unsecure communications. If you intend to keep the HP 3PAR CLI connected to your system for an extended period of time, you must configure your firewall to allow the CLI to remain connected when there is no activity.

Before installing the HP 3PAR CLI on a remote computer, verify that the system meets the following requirements:

•

1 GHz or higher processor.

•

Minimum of 256 MB RAM (1 GB recommended).

•

CD-ROM or DVD-ROM drive (if installing from a CD-ROM).

•

Monitor with 1024 x 768 or better screen resolution.

•

Mouse or compatible pointing device.

Disk Space Requirements

Table 1 (page 12)

lists disk space requirements for installing the HP 3PAR CLI.

Table 1 Free Space Required for Installation

Operating System

Solaris and Linux

Microsoft Windows

HP-UX

Disk Space Required

130 MB

100 MB

1035 MB

Installation

The following sections describe how to install the HP 3PAR CLI on remote systems running compatible versions of Linux, Solaris, and Windows operating systems. You have a choice between a graphical installation and a command line installation. For graphical installation instructions, see

“Graphical

Installation on Windows” (page 13) . For command-line installation instructions, see “Command-Line

12 Installing the HP 3PAR Command Line Interface

Installation on Solaris and Linux” (page 13) . The installation packages default to a command line

installation on UNIX systems and graphical installation on Windows systems.

Before Installation

Prior to installing the HP 3PAR CLI:

•

Shut down all active HP 3PAR CLI sessions.

•

Disable any virus-checking software.

•

Verify that all system requirements have been met. See

“System Requirements” (page 12)

for specifics.

CAUTION:

•

If you install or remove one or more versions of the HP 3PAR CLI simultaneously, the procedure may fail.

•

Do not run multiple installations of the HP 3PAR CLI at the same time.

Graphical Installation on Windows

Installing HP 3PAR CLI can be completed with the InstallAnywhere™ application.

The installation should start automatically once you put the HP 3PAR CLI and SNMP CD into your

CD ROM drive.

If the installation does not start automatically, use the following procedure:

Insert the HP 3PAR CLI and SNMP CD into your drive.

Open the file <D>:\windows\setup.exe where <D> is the letter associated with your drive.

Complete the installation by following the on-screen directions.

The default installation location is C:\Program Files\3PAR\inform_cli_<version>.

Command-Line Installation on Solaris and Linux

To install the HP 3PAR CLI on Solaris platforms:

Insert the HP 3PAR CLI and SNMP CD into your drive.

Start the installation using the setup.bin file:

/cdrom/InFormCLI_and_SNMP/solaris|linux/setup.bin

Log out and log back in.

The default installation location is /opt/3PAR/inform_cli_<version>.

Setting the Path to the CLI on Solaris and Linux

Once the CLI has been installed on your system, the InstallAnywhere application attempts to automatically set the path to the CLI for the root user by adding an entry to your local login file.

The modified file is specific to the shell that you are using during the CLI installation.

If InstallAnywhere is unable to modify the login file, you will need to set the path to the CLI manually.

In order to call commands on the CLI easily from the shell you are using, add the directory where the CLI commands are installed to your shell path.

For example, if you are using the Bourne or bash shells and the commands have been installed in

/opt/3PAR/inform_cli_<version>/bin

, then issue the following commands:

$ PATH=$PATH:/opt/3PAR/inform_cli_<version>/bin

$ export PATH

Installation 13

The <version> is the current release version, for example 3.1.2.

Troubleshooting the Installation

The InstallAnywhere application creates an error log named install.log in the installation directory. If you encounter a failure while installing the HP 3PAR CLI, please provide the install.log

file when contacting your local service provider for technical support.

For Solaris and Linux, if you installed the HP 3PAR CLI in the default location, this log file is located at:

/opt/3PAR/inform_cli_<version>/log/install.log

For Windows, if you installed the HP 3PAR CLI in the default location, this log file is located at:

C:\Program Files\3PAR\inform_cli_<version>\log\install.log

The <version> is the current release version, for example 3.1.2.

Removing the HP 3PAR CLI

The following section describes how to remove HP 3PAR CLI on systems running on Microsoft

Windows, Solaris, and Linux operating environments.

NOTE: Shut down all running applications and disable virus-checking software before proceeding with the following instructions.

On Windows

To remove HP 3PAR CLI from a Windows system:

Close all copies of the administration software currently running on your system.

From the taskbar, click Start

→Programs→3PAR→Uninstall HP 3PAR CLI <version> where

<version> is the current release version, for example 3.1.2.

Result: The Uninstaller window appears.

Follow the instructions that appear in the Uninstaller window.

When prompted, click Finish to finish removing the CLI from your system.

On Solaris and Linux

To remove the HP 3PAR CLI from a Solaris or Linux system:

Bring up a terminal window and log in as root.

NOTE: HP recommends that you log in as root instead of using the su command. If you must use the su command, use su to prevent permission problems that may cause the installation to fail.

Change directories as follows:

/opt/3PAR/inform_cli_<version>/uninstall/uninstall where <version> is the current release version, for example 3.1.1.

Follow the instructions that appear in the Uninstaller to uninstall all HP 3PAR CLI.

When prompted, click Finish to finish removing the HP 3PAR CLI from your system.

Scripting Considerations

If you have scripts that depend on the location of the binaries for any of the HP 3PAR CLI commands, you will need to update your scripts or environment variables to point to the latest version of the

HP 3PAR CLI. As an alternative, if you do not need to keep multiple versions of the HP 3PAR CLI installed, you can change the default install location of the HP 3PAR CLI to a path of your choosing

14 Installing the HP 3PAR Command Line Interface

so that the path stays consistent from release to release. If you do this, you must fully uninstall the previous version using the provided uninstaller before installing a new version.

Multiple versions of the HP 3PAR CLI can reside on the same client system simultaneously. By default, the HP 3PAR CLI is installed in the following locations:

•

On Windows:

C:\Program Files\3PAR\inform_cli_<version>

•

On Solaris or Linux:

/opt/3PAR/inform_cli_<version>

The <version> is the current release version, for example 3.1.2.

Scripting Considerations 15

2 Managing User Accounts and Connections

Learning About User Accounts

In order to access an HP 3PAR storage system you must have a user account. Each HP 3PAR CLI user is assigned a role, and each role is assigned a set of rights. The roles and rights assigned to the CLI user determine which tasks the user can perform with a system. Assign roles to users based on the tasks you intend the users to perform.

Eight roles are defined in the HP 3PAR CLI. See

Table 2 (page 16)

for a description of each role.

There are four standard roles:

•

Browse

•

Edit

•

Super

•

Service

There are also four extended roles:

•

Create

•

Basic Edit

•

3PAR AO

•

3PAR RM

There is no functional difference between standard and extended roles. The extended roles define a set of rights optimized for CLI users with specialized or restricted tasks. For example, assigning a CLI user the Create role allows the user to create virtual volumes and other objects but does not allow the user to remove virtual volumes. To maintain greater control over your system, assign CLI users roles with the minimum set of rights they need to perform their tasks.

•

For procedures to create and remove user accounts, see

“Creating Users” (page 18)

and

“Removing Users” (page 20) .

•

For information about viewing user roles and rights with the CLI see

“Viewing User Roles and

Rights” (page 17)

•

To view a list of roles and all of the rights assigned to the roles, see

“Mapping Roles and

Rights” (page 185)

Table 2 HP 3PAR CLI User Roles

User Roles

Browse

Edit

Super

Service

Create

Basic Edit

Rights Assigned to Roles

Rights are limited to read-only access.

Rights are granted to most operations. For example, creating, editing, and removing virtual volumes and other objects.

Rights are granted to all operations.

Rights are limited to operations required to service the system. Allows limited access to user information and user group resources.

Rights are limited to creating objects. For example, virtual volumes, CPGs, hosts, and schedules.

Rights are similar to the Edit role. For example, creating and editing virtual volumes and other objects. The rights to remove objects are more restricted for the Basic Edit role than the Edit role.

16 Managing User Accounts and Connections

Table 2 HP 3PAR CLI User Roles (continued)

User Roles

3PAR AO

3PAR RM

Rights Assigned to Roles

Rights are limited to internal use by HP for Adaptive Optimization operations.

Rights are limited to internal use by HP for Recovery Manager operations.

Default User Accounts

During the HP 3PAR storage system’s moment of birth operation, the following HP 3PAR CLI user accounts are created:

•

3paradm is a user account with Super rights. This user account is not used by HP personnel and you can modify or delete this user account. Use the 3paradm user account to create new

CLI users. You should change the password of this user.

•

3parcim is a user account with Browse rights. This user account is reserved for use by the HP

3PAR administration tools. The 3parcim user account and password must not be modified or deleted if you intend to use CIM. If CIM will never be used, then the account may be modified or deleted.

•

3parbrowse is a user account with Browse rights. No HP personnel or service providers have access to this user account. The password is randomly created and is unknown to anyone.

This user account is not used by HP personnel and you can modify or delete this user account.

•

3paredit is a user account with Edit rights. No HP personnel or service providers have access to this user account. The password is randomly created and is unknown to anyone. This user account is not used by HP personnel and you can modify or delete this user account.

•

3parsvc is a user account with Super rights. This Super user account is used by the HP 3PAR

Service Processor (SP) to monitor the HP 3PAR storage system. The 3parsvc user account should not be removed. If the SP is being used to monitor the storage server, the SP resets the default password to a randomized value. Changing the password prevents the SP from performing monitoring operations. If the SP is not being used for monitoring and is only used for maintenance activities, the password can be changed. When a maintenance activity takes place, the password for 3parsvc should be set to a defined value; after the maintenance, the SP changes the password to a randomized value again. Once the maintenance is complete, the password can again be changed.

•

3parservice is a user account with Super rights. This Super user account is used by HP personnel and authorized service providers to perform service and diagnostic functions on the system through the interactive CLI. The 3parservice user account should not be removed. The password can be modified by the system administrator. During SP maintenance activities, the password may be reset by the system to allow service to proceed. After the maintenance activities are complete, the password can be reset by the system administrator.

Authenticating and Authorizing CLI Users

Users accessing the system with the HP 3PAR CLI client or Secure Shell (SSH) connections are authenticated and authorized directly on the system. These users are referred to as local users. An

LDAP user is authenticated and authorized using information from a Lightweight Directory Access

Protocol (LDAP) server. A domain user is a user with access to a specific domain. For more information about user accounts, domains, and LDAP, see the HP 3PAR StoreServ Storage Concepts

Guide. For more information about configuring LDAP connections , see

“Configuring LDAP

Connections” (page 21) .

Viewing User Roles and Rights

The showrole command displays information about the roles and rights defined on a system. For more information about the showrole command, see the HP 3PAR Command Line Interface

Viewing User Roles and Rights 17

Reference. For more information about user roles and rights, see

“Learning About User Accounts”

(page 16)

•

To view a list of the available roles on a system, issue the showrole command.

•

To view a list of the available rights on a system, issue the showrole -lstrights command.

•

To view the rights assigned to a specific role, issue the showrole <role_name> command, where <role_name> is the name of the role.

•

To view a list of roles and all of the rights assigned to each role, see

“Mapping Roles and

Rights” (page 185)

•

To view a list of the rights required to use each CLI command, see

“Mapping Rights and CLI

Commands” (page 197)

Creating Users

The first user created should be assigned the Super user role by specifying super for the <role> when issuing the createuser command. For more information about the createuser command, see the HP 3PAR Command Line Interface Reference.

18 Managing User Accounts and Connections

NOTE:

•

The first HP 3PAR storage system user account created must have a role with the right to create additional users. If the first user created has limited rights, the ability to configure the system will be restricted.

•

The <object_set>_set rights include the right to remove the object. For example, the vvset_set right includes the right to remove virtual volume sets.

•

If you are using HP 3PAR Virtual Domains for access control, you must assign users a domain you created in your system or the all domain. See

“Managing HP 3PAR Virtual Domains”

(page 58)

for instructions on creating domains. For more information about domains, see the

HP 3PAR StoreServ Concepts Guide.

•

To create a new user, issue the createuser -c|-e <password> <user_name>

<domain_name> <role> command, where:

◦

-c|-e <password> is either a clear-text (-c) or encrypted (-e) password. A clear-text password must be between 6 and 8 characters in length. An encrypted password must be less than or equal to 31 characters in length. Encrypted passwords are generated by the system. If no password is specified using -c or -e, then you are prompted to enter a clear-text password.

◦

<user_name> is the name of the CLI account user. The user name can be up to 31 characters long. Valid characters include alphanumeric characters, the period symbol

(.), dash symbol (-), and underscore symbol (_). The first character must be alphanumeric or an underscore symbol for users connecting to the system with the HP 3PAR CLI application. To access the system with an SSH connection, the first character of the user name must be alphanumeric.

◦

<domain_name> is the name of the domain to which the user will belong. The domain name can be up to 31 characters long. If you are not using Virtual Domains, specify the all domain. If you are using virtual domains, specify the name of an existing domain in your system.

NOTE: By default, users in systems not using virtual domains are in the all domain.

Users in the all domain have rights over the entire system. The Super, Create, Basic Edit,

3PAR AO, and 3PAR RM roles cannot be restricted and always belong to the all domain.

For more information about the all domain, see the HP 3PAR StoreServ Concepts Guide.

◦

<role> is the role assigned to the user. Valid values include browse, edit, super, service

, create, basic_edit, 3PAR_AO, and 3PAR_RM. The roles and rights assigned to the CLI user determine which tasks a user can perform with a system. For information about viewing the roles and rights defined on a system, see

“Viewing User

Roles and Rights” (page 17) . To view a list of roles and all of the rights assigned to the

roles, see

“Mapping Roles and Rights” (page 185)

You can verify the creation of a new user with the showuser command.

Viewing Users

If you are using Virtual Domains, users with the Super, Create, Basic Edit, 3PAR AO, and 3PAR

RM roles can view all system users across all domains. If the user belongs to a specific domain, the user can only view other users within the same domain.

If you are not using Virtual Domains, the output of the showuser command still displays a Domain column. By default, users in systems not using domains fall into the all domain. For additional details about domains, see the HP 3PAR StoreServ Storage Concepts Guide.

Viewing Users 19

To view a list of users, the user roles, and user domain associations, issue the showuser command.

For more information about the showuser command, see the HP 3PAR Command Line Interface

Reference.

•

To display all the users of a system, issue the showuser command.

•

To display information for a specific user, issue the showuser <user_name> command, where <user_name> is the name of the user.

Removing Users

Removing a user permanently deletes the user account from the system.

To remove a user from the system, issue the removeuser <user_name> command, where

<user_name> is the name of the user.

Adding Users to a Domain

To add a user to an existing domain, issue the setuser -adddomain <domain_name>:<role>

<user_name> command, where:

•

<domain_name> is the name of the domain to which you are adding the specified user.

•

<role> is the role assigned to the user. Permitted values for <role> are browse and edit.

•

<user_name> is the name of the user being added to the specified domain.

NOTE: A user can belong to a maximum of 32 domains. For additional details about domains, see the HP 3PAR StoreServ Storage Concepts Guide.

Removing Users From a Domain

To remove a user from a domain, issue the setuser -rmdomain <domain_name>

<user_name> command, where:

•

<domain_name> is the name of the domain from which the specified user is being removed.

•

<user_name> is the name of the user being removed from the specified domain. You can specify all in place of a specific domain name to remove the user from all domains.

Setting a User’s Default Domain

A user’s default domain is the domain that the user will access upon each working CLI session.

NOTE: Prior to setting a specific domain as a user’s default, the user must previously have been assigned accessibility within that domain.

To set a user’s default domain, issue the setuser -defaultdomain <domain_name>

<user_name> command, where:

•

<domain_name> is the name of the domain which is being set as the default.

•

<user_name> is the name of the user for whom you are assigning a default domain.

For information about default domains, see the HP StoreServ Storage Concepts Guide. For detailed information about the setuser command, see the HP 3PAR Command Line Interface Reference.

Removing a User’s Default Domain

To remove a user’s default domain, issue the setuser -defaultdomain -unset

<user_name> command, where <user_name> is the name of the user for whom you are removing a default domain.

20 Managing User Accounts and Connections

Setting a User’s Current Domain

The current domain refers to the domain in which a user is working during a particular, single CLI session.

To set a user’s current domain, issue the setclienv currentdomain <domain_name> command, where <domain_name> is the domain you wish to set as the working domain for the current CLI session.

Removing a User’s Current Domain

NOTE: When issuing the setclienv currentdomain -unset command, you are not returned to your default domain.

To remove a user’s current domain, issue the setclienv currentdomain -unset command.

Viewing User Connections

To view users currently connected to your system, including their IP addresses and their connection information, issue the showuserconn command.

If you are using domains, prior to issuing the showuserconn command, you must first set the

TPDLISTDOM environment variable or the -listdom global option to display domain information.

If you are working in a Tcl shell, issue the setclienv listdom 1 command to set your system output to display domain information. See

“Listing Domains” (page 49)

for further information.

If the setclienv listdom 1 command is issued when viewing system objects, a Domain column is displayed. Objects not belonging to any domain (no domain) are displayed with a dash

(-) under the Domain column. Otherwise, the domain to which the object belongs appears under the Domain column.

To view a user’s connection to the system, issue the showuserconn <ID> <user_name>

<IP_address> command, where:

•

<ID> is the user’s numeric ID.

•

<user_name> is the user’s assigned name.

•

<IP_address> is the user’s IP address.

For more information about the showuserconn command, see the HP 3PAR Command Line

Interface Reference.

Removing User Connections

To terminate a user’s connection to the system, issue the removeuserconn <ID> <user_name>

<IP_address> command, where:

•

<ID> is the user’s numeric ID.

•

<user_name> is the user’s assigned name.

•

<IP_address> is the user’s IP address.

See the HP 3PAR Command Line Interface Reference for details about this command.

Configuring LDAP Connections

The HP 3PAR OS provides an LDAP client that can be configured to use an LDAP server for authentication and authorization of system users. An LDAP user is similar to a local user; however, an LDAP user is authenticated and authorized using information from an LDAP server. Additionally,

LDAP users’ rights within the system are tied to the groups to which the users belong.

Setting a User’s Current Domain 21

Authentication is the process of using data from the LDAP server to verify a user’s name and the supplied password. Authorization is the process of using data from the LDAP server to determine the user’s group membership and rights in the system.

By default, LDAP users cannot store an SSH public key using the HP 3PAR CLI setsshkey command. Instead, LDAP users can use the setsshkey command by using the allow-ssh-key parameter with the setauthparam command. Assigned rights, domains, and access to the system continues as when the setsshkey command was issued, regardless of any changes to the user’s data in the LDAP server. For more information about using LDAP with HP 3PAR Storage systems, see the HP 3PAR StoreServ Storage Concepts Guide.

CAUTION: Do not create local and LDAP users with the same name. If local and LDAP users have the same name it can cause confusion about where access is controlled.

CAUTION: If the HP 3PAR storage system is operating in Common Criteria mode, do not configure the LDAP server to use an SSH key for authentication. HP 3PAR recommends that you set the allow-ssh-key parameter of the setauthparam CLI command to use the default value of 0 when configuring the LDAP server. This prevents an SSH key from being used for authentication when operating in CC mode. The user’s public key must be stored using the setsshkey CLI command. Storing the user’s public key allows the user’s private key to be validated when entered for login attempts after the first successful LDAP authentication.

Active Directory LDAP Configuration with SASL Binding

To configure your system to use Active Directory with SASL binding, the following process must be performed (detailed instructions follow):

•

Configure connection parameters using the following commands:

◦ setauthparam ldap-server <IP_address>

◦ setauthparam ldap-server-hn <DNS_HostName>

◦ setauthparam kerberos-realm <LDAP_ServiceName>

•

Configure binding (authentication) parameters using the following commands:

◦ setauthparam binding sasl

◦ setauthparam sasl-mechanism <SASL_type>

•

Configure account location parameters using the following commands:

◦ setauthparam accounts-dn <dn_path>

◦ setauthparam account-obj user

◦ setauthparam account-name-attr sAMAccount

◦ setauthparam memberof-attr memberOf

•

Configure group-to-role mapping parameters using the following commands:

◦ setauthparam <map_param> <map_value>

•

Test the authentication/authorization for an Active Directory user account:

◦ checkpassword <user_name>

Each step in the process above is discussed in the following sections. Each section is followed by an example showing the implementation of the instructions described.

22 Managing User Accounts and Connections

NOTE: The examples used to illustrate the procedures described for Active Directory LDAP configuration with SASL binding specifically use GSSAPI as the SASL binding mechanism.

As you will see, a single user is used to determine group hierarchies and path structures used in the system, which are then used to complete the LDAP configuration.

Configuring Connection Parameters

To configure connection parameters:

If not already known, obtain the LDAP server’s host name and Kerberos server information by running the ldapsearch command or using ldp.exe (available as part of the downloadable

Windows Support Tools from Microsoft). You must know the LDAP server’s IP address.

NOTE: If you do not have access to the ldapsearch command, use the ldp.exe command shown below.

•

Issue the ldapsearch command and record the displayed dnsHostName (the value used for the ldap-server-hn parameter) and ldapServiceName (the value used for the kerberos-realm parameter) attributes for later use.

•

Run ldp.exe as follows:

Click Start

→Run.

In the Open box, enter ldp and click OK.

The Ldp window opens.

In the Ldp window, click Connection

→Connect.

In the Server box, enter the Active Directory server’s IP address and click OK.

The root DSE attributes and values are displayed in the right-side pane.

NOTE: In ldp.exe, the Kerberos realm is the portion of the ldapServiceName value that follows the “at” (@) sign and terminates before the semi-colon (;).

In ldapsearch output, the Kerberos realm is the portion of the ldapServiceName value that follows the “at” (@) sign.

Record the displayed dnsHostName (the value used for the ldap-server-hn parameter) and ldapServiceName (the value used for the kerberos-realm parameter) attributes for later use.

Set the address to which the LDAP server will connect by issuing the setauthparam ldap-server <IP_address> command, where <IP_address> is your LDAP server’s IP address.

Set the LDAP server’s host name by issuing the setauthparam ldap-server-hn

<DNS_HostName> command, where <DNS_HostName> is the value displayed by either using the ldapsearch command or ldp.exe in

Step 1 .

Configuring LDAP Connections 23

Set the Kerberos realm by issuing the setauthparam kerberos-realm

<LDAP_ServiceName> command, where <LDAP_ServiceName> is the value displayed by either using the ldapsearch command or ldp.exe in

Step 1

NOTE: The value displayed for the default naming context is used later in

“Configuring

Account Location Parameters” (page 24)

Example:

% ldapsearch -LLL -x -H ldap://192.168.10.13 -b "" -s base dnsHostName ldapServiceName defaultNamingContext dn: dnsHostName: domaincontroller.3par.com

ldapServiceName: 3par.com:[email protected]

defaultNamingContext: DC=3par,DC=com

The example above corresponds to

Step 1

and displays the following:

•

The LDAP server’s IP address is 192.168.10.13.

•

The DNS_HostName is domaincontroller.3par.com.

•

The LDAP_ServiceName is NTDOM1.3PAR.COM.

•

The defaultNamingContext is DC=3par,DC=com.

system1 cli% setauthparam -f ldap-server 192.168.10.13

system1 cli% setauthparam -f ldap-server-hn domaincontroller.3par.com

system1 cli% setauthparam -f kerberos-realm NTDOM1.3PAR.COM

The example above corresponds to

Step 2

through

Step 4

Configuring Binding Parameters

After you have configured the connection parameters to your LDAP server, you must configure the binding (authentication) parameters for users.

Issue the setauthparam binding sasl command.

Issue the setauthparam sasl-mechanism <SASL_type> command, where <type> is specified as PLAIN, DIGEST-MD5, or GSSAPI.

For information on binding types, see “Lightweight Directory Access Protocol” in the HP 3PAR

StoreServ Storage Concepts Guide.

Example: system1 cli% setauthparam -f binding sasl system1 cli% setauthparam -f sasl-mechanism GSSAPI

In the example above, GSSAPI SASL binding is used for authentication.

Configuring Account Location Parameters

To configure the account location parameters:

If you are unsure of the user’s account information, select a known user’s full name (to be entered as the cn value) and run the ldapsearch command using the defaultNamingContext value previously displayed in

“Configuring Connection Parameters”

(page 23)

. Make a note of the group information displayed in the command’s output.

Issue the setauthparam accounts-dn <dn_path> command.

Issue the setauthparam account-obj user command.

24 Managing User Accounts and Connections

Issue the setauthparam account-name-attr sAMAccount command.

Issue the setauthparam memberof-attr memberOf command.

NOTE: You must know the user’s password in order to successfully use the checkpassword command.

Issue the checkpassword command to obtain information about the user’s group memberships from the LDAP server.

Example:

% ldapsearch -LLL -x -H ldaps://192.168.10.13 -D 'NTDOM1\joeadmin' -W -b

DC=3par,DC=com -s sub '(cn=3PARuser)' dn

Enter LDAP Password: dn: CN=3PAR User,OU=Engineering,OU=Users,DC=3par,DC=com

The example above corresponds to

Step 1 , and displays the following:

• joadmin is the user name of the NT Windows domain (NTDOM1) administrator searching for group information for user 3PARuser (cn=3PAR User).

• dn: CN=3PAR User,OU=Engineering,OU=Users,DC=3par,DC=com displays user locations in the LDAP server directory information tree.

system1 cli% setauthparam -f accounts-dn OU=Users,DC=3par,DC=com system1 cli% setauthparam -f account-obj user system1 cli% setauthparam -f account-name-attr sAMAccountName system1 cli% setauthparam -f memberof-attr memberOf

The example above corresponds to

Step 2

through

Step 5

•

The Users group within the 3par group is set as the basis for any user search when authenticating with the LDAP server.

•

The values user, SAMAccountName, and memberOf for the account-obj, account-name-attr

, and memberof-attr parameters are typical of Active Directory configurations.

system1 cli% checkpassword 3paruser password:

+ attempting authentication and authorization using system-local data

+ authentication denied: unknown username

+ attempting authentication and authorization using LDAP

+ connecting to LDAP server using URI: ldaps://192.168.10.13

+ simple bind to LDAP user 3paruser for DN uid=3paruser,ou=people,dc=ldaptest,dc=3par,dc=com

+ searching LDAP using:

search base: ou=people,dc=ldaptest,dc=3par,dc=com

filter: (&(objectClass=posixAccount)(uid=3paruser))

for attributes: gidNumber

+ search result DN: uid=3paruser,ou=people,dc=ldaptest,dc=3par,dc=com

+ search result: gidNumber: 2345

+ searching LDAP using:

search base: ou=groups,dc=ldaptest,dc=3par,dc=com

filter:

(&(objectClass=posixGroup)(|(gidNumber=2345)(memberUid=3paruser)))

for attributes: cn

+ search result DN: cn=software,ou=groups,dc=ldaptest,dc=3par,dc=com

+ search result: cn: software

+ search result DN: cn=engineering,ou=groups,dc=ldaptest,dc=3par,dc=com

+ search result: cn: engineering

Configuring LDAP Connections 25

+ search result DN: cn=hardware,ou=groups,dc=ldaptest,dc=3par,dc=com

+ search result: cn: hardware

+ mapping rule: super mapped to by software

+ rule match: super mapped to by software

+ mapping rule: edit mapped to by engineering

+ rule match: edit mapped to by engineering

+ mapping rule: browse mapped to by hardware

+ rule match: browse mapped to by hardware user 3paruser is authenticated and authorized

•

The example above corresponds to

Step 6 , and shows that 3PARuser is a member of the

following hierarchy of groups:

◦

Engineering

◦

Software

◦

Eng

◦

Golfers

•

In this example, 3PARuser is not yet authenticated or authorized because 3PARuser’s group-to-role mapping has not been configured.

Configuring Group-to-Role Mapping Parameters

Once you have configured the group location parameters, you must now decide what role you wish to assign the users for a given group. To configure group-to-role mapping:

Issue the setauthparam <map-param> <map-value> command, where:

•

<map-param> is one of the following:

◦ super-map

—provides Super user rights within the specified group.

◦ service-map

—provides Service user rights within the specified group.

◦ edit-map

—provides Edit user rights within the specified group.

◦ browse-map

—provides Browse user rights within the specified group.

◦ create-map

—provides Create user rights within the specified group.

◦ basic_edit-map

—provides Basic Edit user rights within the specified group.

◦

3PAR_AO-map

—provides 3PAR AO user rights within the specified group.

◦

3PAR_RM-map

—provides 3PAR RM user rights within the specified group.

•

<map-value> is the group to which the user has membership. You can specify multiple groups with multiple <map-value> arguments.

For Active Directory, the group is displayed as a string of information, as shown in the following example:

CN=Software,CN=Users,DC=ACME,DC=com

NOTE: The HP 3PAR Management Console (HP 3PAR MC) refers to <map-param> specifiers as Authorization Groups.

Repeat

Step 1

above if you wish to assign users a different role for another group to which that user has membership.

26 Managing User Accounts and Connections

Issue the checkpassword command to verify that the users have the roles you assigned for the desired groups. Use a member of a specific group to verify the role.

Example: system1 cli% setauthparam -f edit-map CN=Software,CN=Users,DC=3par,DC=com system1 cli% setauthparam -f browse-map CN=Eng,CN=Users,DC=3par,DC=com

In the example above:

•

Users belonging to the Software group are configured to have Edit rights within the system.

•

Users belonging the Eng group are configured to have Browse rights within the system.

system1 cli% checkpassword 3PARuser

...

+ search result: memberOf: CN=Software,CN=Users,DC=3par,DC=com

+ search result: memberOf: CN=Eng,CN=Users,DC=3par,DC=com

+ search result: memberOf: CN=Golfers,CN=Users,DC=3par,DC=com

+ mapping rule: edit mapped to by CN=Software,CN=Users,DC=3par,DC=com

+ rule match: edit mapped to by CN=Software,CN=Users,DC=3par,DC=com

+ mapping rule: browse mapped to by CN=Eng,CN=Users,DC=3par,DC=com

+ rule match: browse mapped to by CN=Eng,CN=Users,DC=3par,DC=com user 3PARuser is authenticated and authorized

In the example above:

•

3PARuser is a member of the Software group and is assigned Edit rights within the system.

•

Although 3PARuser is also a member of the Eng group, the Edit rights associated with the Software group supersede the Browse rights associated with the Eng group.

•

The mapping rules set for 3PARuser are applied to all members of the Software group and Eng groups; all Software group members have Edit rights within the system and all Eng group members have Browse rights within the system.

Active Directory LDAP Configuration with Simple Binding Over SSL

To configure Active Directory with simple binding over SSL, follow these procedures using the specified commands (detailed instructions follow):

•

Configure connection parameters using the following commands:

◦ setauthparam ldap-server <IP_address>

◦ setauthparam ldap-server-hn <DNS_HostName>

•

Configure binding (authentication) parameters using the following commands:

◦ setauthparam binding simple

◦ setauthparam user-atter <DN_attribute>

Configuring LDAP Connections 27

•

(Optional) Set the CA certificate using the following command:

◦ setauthparam ladp-ssl-cacert <certificate>

•

Configure account location parameters using the following commands:

◦ setauthparam accounts-dn <DN_path>

◦ setauthparam account-obj user

◦ setauthparam account-name-attr sAMAccount

◦ setauthparam memberof-attr memberOf

◦ checkpassword <user_name>

•

Configure group-to-role mapping parameters using the following commands:

◦ setauthparam <map_param> <map_value>

◦ checkpassword <user_name>

Each step in the process above is discussed in the following sections. Each section is followed by an example showing the implementation of the instructions described.

Configuring Connection Parameters

To configure connection parameters:

If not already known, obtain the LDAP server’s host name by running the ldapsearch command or using ldp.exe (available as part of the downloadable Windows Support Tools from Microsoft). You must know the LDAP server’s IP address.

NOTE: If you do not have access to the ldapsearch command, use the ldp.exe command.

•

Issue the ldapsearch command and record the displayed dnsHostName (the value used for the ldap-server-hn parameter; this is only necessary when setting CA certificates).

•

Run ldp.exe as follows:

Click Start

→Run.

In the Open box, enter ldp and click OK.

The Ldp window opens.

In the Ldp window, click Connection

→Connect.

In the Server box, enter the Active Directory server’s IP address and click OK.

The root DSE attributes and values are displayed in the right-side pane.

Record the displayed dnsHostName (the value used for the ldap-server-hn parameter; only necessary if setting CA certificates).

Set the address to which the LDAP server will connect by issuing the setauthparam ldap-server <IP_address> command, where <IP_address> is your LDAP server’s IP address.

28 Managing User Accounts and Connections

Set the LDAP server’s host name by issuing the setauthparam ldap-server-hn

<DNS_HostName> command, where <DNS_HostName> is the value displayed by either using the ldapsearch command or ldp.exe in

Step 1 .

NOTE: The value displayed for the defaultNamingContext is used later in

“Configuring

Account Location Parameters” (page 24)

Example:

% ldapsearch -LLL -x -H ldap://192.168.10.13 -b "" -s base dnsHostName ldapServiceName defaultNamingContext dn: dnsHostName: domaincontroller.3par.com

ldapServiceName: 3par.com:[email protected]

defaultNamingContext: DC=3par,DC=com

The example above corresponds to

Step 1

and displays the following:

•

The LDAP server’s IP address is 192.168.10.13.

•

The DNS_HostName is domaincontroller.3par.com.

•

The defaultNamingContext is DC=3par,DC=com.

system1 cli% setauthparam -f ldap-server 192.168.10.13

system1 cli% setauthparam -f ldap-server-hn domaincontroller.3par.com

The example above corresponds to

Step 2

through

Step 3

Configuring Binding Parameters

After you have configured the connection parameters to your LDAP server, you must configure the binding (authentication) parameters for users.

Issue the setauthparam binding simple command.

Example: system1 cli% setauthparam -f binding simple

Issue the setauthparam user-atter <DN_attribute> command to set the attribute used to form a DN to the Windows domain.

Example setauthparam -f user-attr NTDOM1\\

In the example above, the Windows domain is NTDOM1.

Configuring the CA Certificate

To configure the CA certificate:

Obtain the location of the CA certificate from the Active Directory server’s administrator.

NOTE: If the certificate ends in the file extension .crt, it will need to be converted to a form compatible with the setauthparam command.

If necessary, convert the certificate to .cer file format. On a Windows system: a.

Double-click the certificate.

Configuring LDAP Connections 29

Select the Details tab.

Click Copy to File....

Click Next.

Select Base-64 encoded x.5098 format.

Click Next.

Click Browse... and select a filename for the certificate (ending in the .cer file extension) and a folder in which the certificate will be stored.

Click Next and then Finish.

Or, use the openssl x509 program.

Set the certificate using the setauthparam ladp-ssl-cacert <certicate> command, where <certificate> is the name of the certificate you previously located or converted.

Example: openssl x509 -inform DER -in ca.crt -outform PEM -out ca.cer

In the example above, the openssl x509 command is used to convert the CA certificate from ca.crt format to ca.cer format, which can then be used with the setauthparam command.

setauthparam -f ldap-ssl-cacert ca.cer

In the example above, the setauthparam command is issued to set the CA certificate to the ca.cer

file.

Configuring Account Location Parameters

To configure the account location parameters:

“Configuring Connection Parameters”

(page 28)

. Make a note of the group information displayed in the command’s output.

Issue the setauthparam accounts-dn <DN_path> command.

Issue the setauthparam account-obj user command.

Issue the setauthparam account-name-attr sAMAccount command.

Issue the setauthparam memberof-attr memberOf command.

NOTE: You must know the user’s password in order to successfully use the checkpassword command.

Issue the checkpassword command to obtain information about the user’s group memberships from the LDAP server.

Example:

% ldapsearch -LLL -x -H ldap://192.168.10.13 -D 'NTDOM1\joeadmin' -W -b

DC=3par,DC=com -s sub '(cn=3PARuser)' dn

Enter LDAP Password: dn: CN=3PAR User,OU=Engineering,OU=Users,DC=3par,DC=com

30 Managing User Accounts and Connections

The example above corresponds to

Step 1 , and displays the following:

• joadmin is the user name of the NT Windows domain (NTDOM1) administrator searching for group information for user 3PARuser (cn=3PARuser).

• dn: CN=3PAR User,OU=Engineering,OU=Users,DC=3par,DC=com displays user locations in the LDAP server directory information tree.

The example above corresponds to

Step 2

through

Step 5

. The following can be surmised based on the group information gathered from running the ldapsearch command:

•

The Users group within the 3par group is set as the basis for any user search when authenticating with the LDAP server.

•

The values user,SAMAccountName, and memberOf for the account-obj, account-name-attr

, and memberof-attr parameters are typical of Active Directory configurations.

system1 cli% checkpassword 3PARuser password:

+ attempting authentication and authorization using system-local data

+ authentication denied: unknown username

+ attempting authentication and authorization using LDAP

+ using Kerberos configuration file:

[domain_realm]

domaincontroller.3par.com = NTDOM1.3PAR.COM

[realms]

NTDOM1.3PAR.COM = {

kdc = 192.168.10.13

}

+ temporarily setting name-to-address mapping: domaincontroller.3par.com ->

192.168.10.13

+ attempting to obtain credentials for [email protected]

+ connecting to LDAP server using URI: ldap://192.168.10.13

+ binding to user 3PARuser with SASL mechanism GSSAPI

+ searching LDAP using:

search base: OU=Users,DC=3par,DC=com

filter: (&(objectClass=user)(sAMAccountName=3PARuser))

for attribute: memberOf

+ search result DN: CN=3PARuser,OU=Engineering,OU=Users,DC=3par,DC=com

+ search result: memberOf: CN=Software,CN=Users,DC=3par,DC=com

+ search result: memberOf: CN=Eng,CN=Users,DC=3par,DC=com

+ search result: memberOf: CN=Golfers,CN=Users,DC=3par,DC=com

+ authorization denied: no user groups match mapping rules user 3PARuser is not authenticated or not authorized

•

The example above corresponds to

Step 6 , and displays that 3PARuser is a member of the

following hierarchy of groups:

◦

Engineering

◦

Software

Configuring LDAP Connections 31

◦

Eng

◦

Golfers

•

In this example, 3PARuser is not yet authenticated or authorized because 3PARuser’s group-to-role mapping has not been configured.

Configuring Group-To-Role Mapping Parameters

Once you have configured the group location parameters, you must now decide what role you wish to assign the users for a given group. To configure group-to-role mapping:

Issue the setauthparam <map_param> <map_value> command, where:

•

<map_param> is one of the following:

◦ super-map

—provides Super user rights within the specified group.

◦ service-map

—provides Service user rights within the specified group.

◦ edit-map

—provides Edit user rights within the specified group.

◦ browse-map

—provides Browse user rights within the specified group.

◦ create-map

—provides Create user rights within the specified group.

◦ basic_edit-map

—provides Basic Edit user rights within the specified group.

◦

3PAR_AO-map

—provides 3PAR AO user rights within the specified group.

◦

3PAR_RM-map

—provides 3PAR RM user rights within the specified group.

•

<map_value> is the group to which the user has membership. You can specify multiple groups with multiple <map_value> arguments.

For Active Directory, the group is displayed as a string of information as shown in the following example:

CN=Software,CN=Users,DC=ACME,DC=com

Repeat

Step 1

above if you wish to assign users a different role for another group to which that user has membership.

32 Managing User Accounts and Connections

Issue the checkpassword command to verify that the users have the roles you assigned for the desired groups. Use a member of a specific group to verify the role.

Example: system1 cli% setauthparam -f edit-map CN=Software,CN=Users,DC=3par,DC=com system1 cli% setauthparam -f browse-map CN=Eng,CN=Users,DC=3par,DC=com

In the example above:

•

Users belonging to the Software group are configured to have Edit rights within the system.

•

Users belonging the Eng group are configured to have Browse rights within the system.

system1 cli% checkpassword 3PARuser

...

+ search result: memberOf: CN=Software,CN=Users,DC=3par,DC=com

+ search result: memberOf: CN=Eng,CN=Users,DC=3par,DC=com

+ search result: memberOf: CN=Golfers,CN=Users,DC=3par,DC=com

+ mapping rule: edit mapped to by CN=Software,CN=Users,DC=3par,DC=com

+ rule match: edit mapped to by CN=Software,CN=Users,DC=3par,DC=com

+ mapping rule: browse mapped to by CN=Eng,CN=Users,DC=3par,DC=com

+ rule match: browse mapped to by CN=Eng,CN=Users,DC=3par,DC=com user 3PARuser is authenticated and authorized

In the example above:

•

3PARuser is found to be a member of the Software group and is assigned Edit rights within the system.

•

Although 3PARuser is also a member of the Eng group, the Edit rights associated with the Software group supersede the Browse rights associated with the Eng group.

•

The mapping rules set for 3PARuser are applied to all members of the Software group and Eng group; all Software group members have Edit rights within the system and all

Eng group members have Browse rights within the system.

OpenLDAP Configuration with Simple Binding Over SSL

To configure your system to use OpenLDAP with simple binding over SSL, the following process must be performed (detailed instructions follow):

•

Configure connection parameters using the following command:

◦ setauthparam ldap-server <IP_address>

◦ setauthparam ldap-ssl 1

•

Configure binding (authentication) parameters using the following commands:

◦ setauthparam binding <binding_type>

◦ setauthparam user-dn-base <value>

◦ setauthparam user-attr <attribute>

•

Configure group location parameters using the following commands:

◦ setauthparam groups-dn <value>

◦ setauthparam group-object <group_object_class>

Configuring LDAP Connections 33

◦ setauthparam group-name-attr <attribute>

◦ setauthparam member-attr <member_attribute>

•

Configure group-to-role mapping parameters using the following commands:

◦ setauthparam <map_param> <map_value>

◦ checkpassword <user_name>

Different schemas can be used for user and group information with OpenLDAP. The instructions and example that follow describe configuration of the system using Posix users and groups.

Configuring Connection Parameters

To configure connection parameters, issue the setauthparam ldap-server

<IP_address> command, where <IP_address> is the OpenLDAP server’s IP address.

Issue the setauthparam ldap-ssl 1 command.

Example: system1 cli% setauthparam -f ldap-server 192.168.10.13

system1 cli% setauthparam -f ldap-ssl 1

In the example above:

•

The OpenLDAP server’s IP address is 192.168.10.13.

•

SSL security is activated using the 1 parameter.

Configuring Binding Parameters

After you have configured the connection parameters to your LDAP server, you must configure the binding (authentication) parameters for users.

To configure binding parameters:

Issue the setauthparam binding <binding_type> command.

Issue the setauthparam user-dn-base <value> command, where <value> is the base of the subtree where user information is kept in the OpenLDAP server directory information tree.

34 Managing User Accounts and Connections

Issue the setauthparam user-attr <attribute> command, where <attribute> is the name of the attribute holding the user’s <user_name>.

Example: system1 cli% setauthparam -f binding simple

In the example above, simple binding is specified as the binding mechanism.

system1 cli% setauthparam -f user-dn-base ou=people,dc=ldaptest,dc=3par,dc=com

In the example above, the base of the user entries in the OpenLDAP server directory information tree is ou=people,dc=ldaptest,dc=3par,dc=com.

system1 cli% setauthparam -f user-attr uid

In the example above, uid is the attribute with the value of the user’s user name of the posixAccount object class.

Configuring Group Location Parameters

To configure group location parameters, perform the following:

Issue the setauthparam groups-dn <value> command, where <value> is the basis of the search for objects holding group information in the subtree of the directory information tree.

Issue the setauthparam group-object <group_object_class> command.

Issue the setauthparam group-name-attr <attribute> command, where

<attribute> is the group object’s attribute that holds the group name.

Issue the setauthparam member-attr <member_attribute> command, where

<member_attribute> is attribute that holds the names of the users in the group.

Example: system1 cli% setauthparam -f groups-dn ou=groups,dc=ldaptest,dc=3par,dc=com

In the example above, ou=groups,dc=ldaptest,dc=3par,dc=com is the search base for objects holding group information in the directory information subtree.

system1 cli% setauthparam -f group-obj posixGroup system1 cli% setauthparam -f group-name-attr cn system1 cli% setauthparam -f member-attr memberUid

In the example above:

• posixGroup is the group object class.

• cn is the attribute of the posixGroup, which has a value of the group’s name.

• memberUid is the attribute with the value of the user’s <user_name>.

Configuring Group-To-Role Mapping Parameters

Once you have configured the group location parameters, you must now decide what role you wish to assign the users for a given group. To configure group-to-role mapping:

Configuring LDAP Connections 35

Issue the setauthparam <map_param> <map_value> command, where:

•

<map_param> is one of the following:

◦ super-map

—provides Super user rights within the specified group.

◦ service-map

—provides Service user rights within the specified group.

◦ edit-map

—provides Edit user rights within the specified group.

◦ browse-map

—provides Browse user rights within the specified group.

◦ create-map

—provides Create user rights within the specified group.

◦ basic_edit-map

—provides Basic Edit user rights within the specified group.

◦

3PAR_AO-map

—provides 3PAR AO user rights within the specified group.

◦

3PAR_RM-map

—provides 3PAR RM user rights within the specified group.

•

<map_value> is the group to which the user has membership. You can specify multiple groups with multiple <map_value> arguments.

Repeat

Step 1

above if you wish to assign users a different role for another group to which that user has membership.

36 Managing User Accounts and Connections

Issue the checkpassword command to verify that the users have the roles you assigned for the desired groups. Use a member of a specific group to verify the role.

Example: system1 cli% setauthparam -f super-map software system1 cli% setauthparam -f edit-map engineering system1 cli% setauthparam -f browse-map hardware

In the example above:

•

Users belonging to the software group are configured to have Super rights within the system.

•

Users belonging to the engineering group are configured to have Edit rights within the system.

•

Users belonging to the hardware group are configured to have Browse rights within the system.

system1 cli% checkpassword 3paruser password:

+ attempting authentication and authorization using system-local data

+ authentication denied: unknown username

+ attempting authentication and authorization using LDAP

+ connecting to LDAP server using URI: ldaps://192.168.10.13

+ simple bind to LDAP user 3paruser for DN uid=3paruser,ou=people,dc=ldaptest,dc=3par,dc=com

+ searching LDAP using:

search base: ou=people,dc=ldaptest,dc=3par,dc=com

filter: (&(objectClass=posixAccount)(uid=3paruser))

for attributes: gidNumber

+ search result DN: uid=3paruser,ou=people,dc=ldaptest,dc=3par,dc=com

+ search result: gidNumber: 2345

+ searching LDAP using:

search base: ou=groups,dc=ldaptest,dc=3par,dc=com

filter:

(&(objectClass=posixGroup)(|(gidNumber=2345)(memberUid=3paruser)))

for attributes: cn

+ search result DN: cn=software,ou=groups,dc=ldaptest,dc=3par,dc=com

+ search result: cn: software

+ search result DN: cn=engineering,ou=groups,dc=ldaptest,dc=3par,dc=com

+ search result: cn: engineering

+ search result DN: cn=hardware,ou=groups,dc=ldaptest,dc=3par,dc=com

+ search result: cn: hardware

+ mapping rule: super mapped to by software

+ rule match: super mapped to by software

+ mapping rule: edit mapped to by engineering

+ rule match: edit mapped to by engineering

+ mapping rule: browse mapped to by hardware

+ rule match: browse mapped to by hardware user 3paruser is authenticated and authorized

In the example above:

•

User 3PARuser is found to be a member of the software group and is assigned Super rights within the system.

•

Although 3PARuser is also a member of the engineering and hardware groups, the

Super rights associated with the Software group supersede the Edit and Browse rights associated with the engineering and software groups.

•

The mapping rules set for 3PARuser are applied to all members of the software, engineering

, and hardware groups; all software group members have Super

Configuring LDAP Connections 37

rights within the system, all engineering group members have Edit rights within the system, and all hardware group members have Browse rights within the system.

Configuring LDAP Connections on Systems Using Domains

LDAP is also available for systems using virtual domains for access control. The configuration process is nearly identical to configuring LDAP on non-Domain systems, with the only difference being an additional authorization step to map a user’s group to a domain. For information about

LDAP and domains, see “Lightweight Directory Access Protocol” in the HP 3PAR StoreServ Storage

Concepts Guide.

To configure your system to use an Active Directory LDAP server using SASL binding, the following process must be performed (detailed instructions follow):

•

Configure connection parameters using the following commands:

◦ setauthparam ldap-server <IP_address>

◦ setauthparam ldap-server-hn <DNS_HostName>

◦ setauthparam kerberos-realm <LDAP_ServiceName>

•

Configure binding (authentication) parameters using the following commands:

◦ setauthparam binding sasl

◦ setauthparam sasl-mechanism <SASL_type>

•

Configure account location parameters using the following commands:

◦ setauthparam accounts-dn <DN_path>

◦ setauthparam account-obj user

◦ setauthparam account-name-attr sAMAccount

◦ setauthparam memberof-attr memberOf

◦ checkpassword <user_name>

•

Configure group-to-role mapping parameters using the following command: setauthparam <map_param> <map_value>

•

Configure group-to-domain mapping parameters using the following commands:

◦ setauthparam group-obj group

◦ setauthparam domain-name-attr <attribute>

, and optionally setauthparam domain-name-prefix <prefix>

◦ checkpassword <user_name>

The following instructions describe how to set up an Active Directory LDAP connection on a system using Domains:

Follow the directions as described in the following sections: a.

“Configuring Connection Parameters” (page 23)

“Configuring Binding Parameters” (page 24)

“Configuring Account Location Parameters” (page 24)

“Configuring Group-to-Role Mapping Parameters” (page 26)

; however, do not issue the checkpassword command.

38 Managing User Accounts and Connections

Configure the group-to-domain mapping parameters, as follows:

•

Issue the setauthparam domain-name-attr <attribute> command, where

<attribute> is the name of an attribute that holds the potential domain name. A common parameter to specify as the <attribute> is name.

•

(Optional.) Issue the setauthparam domain-name-prefix <prefix> command, where <prefix> is the start point of the domain name search within the information returned from the domain-name-attr <attribute> parameter described above. An example parameter to specify as the <prefix> is SystemDomain=.

Issue the checkpassword command to verify that the users have the roles you assigned for the desired groups and the group-to-domain mapping is correct. Use a member of a specific group to verify the role.

Example using only the domain-name-attr parameter: system cli% setauthparam domain-name-attr name

The example above corresponds to the first bullet in

Step 2

. As shown, name is the attribute used as the basis of the domain name search.

system1 cli% checkpassword 3PARuser

...

+ search result: memberOf: CN=Software,CN=Users,DC=3par,DC=com

+ search result: memberOf: CN=Eng,CN=Users,DC=3par,DC=com

+ search result: memberOf: CN=Golfers,CN=Users,DC=3par,DC=com

+ mapping rule: edit mapped to by CN=Software,CN=Users,DC=3par,DC=com

+ rule match: edit mapped to by CN=Software,CN=Users,DC=3par,DC=com

+ mapping rule: browse mapped to by CN=Eng,CN=Users,DC=3par,DC=com

+ rule match: browse mapped to by CN=Eng,CN=Users,DC=3par,DC=com

+ searching LDAP using:

search base: CN=Software Group,CN=Users,DC=3par,DC=com

filter: (objectClass=group)

for attributes: name

+ search result DN: CN=Software Group,CN=Users,DC=3par,DC=com

+ search result: name: Software Group

+ group "CN=Software Group,CN=Users,DC=3par,DC=com" has potential domain Software_Group

(transformed from "Software Group")

+ searching LDAP using:

search base: CN=Eng,CN=Users,DC=hq,DC=3par,DC=com

filter: (objectClass=group)

for attributes: name

+ search result DN: CN=Eng,CN=Users,DC=hq,DC=3par,DC=com

+ search result: name: Engineering

+ group "CN=Eng,CN=Users,DC=hq,DC=3par,DC=com" has potential domain Engineering

+ domain match: Engineering mapped to browse

+ domain match: Software_Group mapped to edit user 3PARuser is authenticated and authorized

The example above corresponds to

Step 3

and displays the following:

•

3PARuser is found to be a member of the Software group with Edit rights. The Software group is mapped to the Software_Group domain. 3PARuser is assigned Edit rights within the Software domain.

•

3PARuser is also found to be a member of the Eng group with Browse rights. The Eng group is mapped to the Engineering domain. 3PARuser is assigned Browse rights within the Eng domain.

Configuring LDAP Connections on Systems Using Domains 39

Example using the domain-name-prefix parameter: system cli% setauthparam domain-name-attr description system cli% setauthparam domain-name-prefix SystemDomain=

The example above corresponds to the second bullet in

Step 2

. As shown, SystemDomain= is the start point of the domain name search within the information returned from the domain-name-attr description parameter described above. The text following

SystemDomain= is treated as the potential domain name.

system1 cli% checkpassword 3paruser

...

+ temporarily setting name-to-address mapping: domaincontroller.3par.com ->

192.168.10.13

+ attempting to obtain credentials for [email protected]

+ connecting to LDAP server using URI: ldap://192.168.10.13

+ binding to user 3paruser with SASL mechanism GSSAPI

+ searching LDAP using:

search base: OU=Users,DC=3par,DC=COM

filter: (&(objectClass=user)(sAMAccountName=3paruser))

for attributes: memberOf

+ search result DN: CN=3PAR User,OU=Eng,OU=Users,DC=3par,DC=COM

+ search result: memberOf: CN=Software,CN=Users,DC=3par,DC=com

+ search result: memberOf: CN=Eng,CN=Users,DC=3par,DC=com

+ mapping rule: edit mapped to by CN=Software,CN=Users,DC=3par,DC=com

+ rule match: edit mapped to by CN=Software,CN=Users,DC=3par,DC=com

+ mapping rule: browse mapped to by CN=Eng,CN=Users,DC=3par,DC=com

+ rule match: browse mapped to by CN=Eng,CN=Users,DC=3par,DC=com

+ searching LDAP using:

search base: CN=Software,CN=Users,DC=3par,DC=com

filter: (objectClass=group)

for attributes: description

+ search result DN: CN=Software,CN=Users,DC=3par,DC=com

+ search result: description: Software

+ group "CN=Software,CN=Users,DC=3par,DC=com" has potential domain Software

+ searching LDAP using:

search base: CN=Eng,CN=Users,DC=3par,DC=com

filter: (objectClass=group)

for attributes: description

+ search result DN: CN=Eng,CN=Users,DC=3par,DC=com

+ search result: description: Engineering Group, SystemDomain=engineering-group-dom

+ group "CN=Eng,CN=Users,DC=3par,DC=com" has potential domain engineering-group-dom

(transformed from "Engineering Group, SystemDomain=engineering-group-dom")

+ domain match: Engineering mapped to browse

+ domain match: Software mapped to edit user 3paruser is authenticated and authorized

40 Managing User Accounts and Connections

3 Running the HP 3PAR Command Line Interface

After the CLI is installed (as described in

“Installing the HP 3PAR Command Line Interface” (page 12)

) and a user account is set up (as described in

“Managing User Accounts and Connections”

(page 16)

), a CLI connection requires the following information:

•

System name or IP address

•

User name

•

Password

You are prompted as follows when running the CLI: system: user: password:

The example above displays the simplest way to connect to the CLI.

In addition to the method described above, you can also:

•

Use environment variables and global options to customize the CLI ( “Global Options and

Environment Variables” (page 41)

•

Set up a secure connection using SSL (

“Using SSL” (page 44)

•

Issue stand-alone CLI commands from a shell prompt in Solaris or Linux, or from a Windows command prompt (

“Stand-alone Commands” (page 52)

•

Use SSH to encrypt all traffic between the client and server, including passwords ( “SSH”

(page 52)

Global Options and Environment Variables

Global options are provided to help configure the CLI and control the operation of the system.

Environment variables are provided to customize the CLI. The global CLI options and environment variables are listed in

“Global CLI Options and Environment Variables” (page 42) .

•

You can use the global options with the CLI program and individual CLI commands.

•

When used with the CLI program, global options remain in effect until you exit the Tcl shell

(for information about the Tcl shell, see

“Stand-alone Commands” (page 52) ). The following

example shows the –sys option used with the CLI program for a system named betasystem1:

$ cli –sys betasystem1

•

When used with individual commands, global options are in effect only for that command.

The following example shows the –pwf option used with the showsysmgr CLI command:

$ showsysmgr –pwf ~/my–pwfile

•

Global options, when used, override environment variables.

NOTE: Global options cannot be specified on the command line for commands issued from a

Tcl shell. Global options must be specified before starting a Tcl shell.

You can use environment variables when configuring the CLI.

Global Options and Environment Variables 41

NOTE: Environment variables can only be used if the CLI is set up remotely. Environment variables cannot be used if you are accessing the CLI through SSH.

Table 3 Global CLI Options and Environment Variables

Global Option

–sockssl

–sys <system_name>

–password <encrypw>

–pwf <password_file>

–user <user_name>

Environment Variable

TPDSOCKSSL

TPDSYSNAME

––

TPDPWFILE

––

Specifies...

that the connection between the client and server is secure.

This is the default setting. For additional information, see

“Using SSL” (page 44)

the system name of the system you are accessing. For additional information, see

“Setting the TPDSYSNAME

Environment Variable” (page 45)

the encrypted password. This value should be protected for security purposes. For additional information, see

“Setting

Your Name and Password” (page 46) .

the password file the system references upon starting the

CLI. This value should be protected for security purposes.

For additional information, see

“Setting Your Name and

Password” (page 46) .

your user name. For additional information, see

“Setting

Your Name and Password” (page 46) . Specifying the -user

option also requires specifying the -password option. These options override the -pwf option.

CAUTION: By setting the system name, user name, and password using environment variables, you are not prompted for this information when running the CLI, which can be useful for scripting. However, passwords must be kept secure.

Using encrypted passwords in scripts, using an encrypted pwfile, or the encrypted password on the command line raises the risk of password exposure. It is imperative that the script, pwfile, or command line history file be strictly maintained to avoid compromise of the encrypted password. Failure to do so can leave the user open to impersonation by anyone with access to the encrypted string.

-nosockssl

––

– csvtable

-listdom

-nohdtot

-hafter

NOTPDSOCKSSL

TPDCACHEDIR

TPDSTARTFILE

TPDCSVTABLE

TPDLISTDOM

TPDNOHDTOT

TPDHAFTER that the CLI client should attempt to connect to the storage server on port 5782, without using SSL. This makes the connection insecure, and all data including authentication data passes in plain text packets.

the location of the cache directory where the code that determines the version of the HP 3PAR software on the system resides. For additional information, see

“Caching

Client Bytecode” (page 47)

the Tcl script that the system sources before entering the command loop. For additional information, see

“Startup

Files” (page 48) .

that commands that use the table formatting routines will print comma-separated output. For additional information, see

“Comma Separated Values” (page 48) .

that domains are listed. For additional information, see

“Listing Domains” (page 49)

that headers and totals are not printed after commands are executed. For additional information, see

“Table Headers and Totals” (page 50)

the number of lines after which the header is printed again.

For additional information,

“Table Headers and Totals”

(page 50)

42 Running the HP 3PAR Command Line Interface

Table 3 Global CLI Options and Environment Variables (continued)

Global Option

––

–v

Environment Variable

TPDFORCE

––

Specifies...

that all commands are forced and do not return confirmation prompts before executing. For additional information, see

“Forcing Commands” (page 51) .

the client-side version information, in the event of a version mismatch or other problem that prevents connection with a server. This option can only be used with the cli command.

For additional information, see the HP 3PAR Command Line

Interface Reference.

General Control and Help Commands

Table 4 (page 43)

shows the general control and help commands that you can use to view help text while using the HP 3PAR CLI.

Table 4 General Control Commands

Command cmore exit help –search <topic> clihelp –search <topic> help <command> clihelp <command> clihelp –col <command>

<command> –h

Action

Pages the output of commands. Valid syntax for using this command is cmore <command>.

Terminates the program.

Lists all commands or details for the specified topic.

Specifying –search <topic> allows you to search command help by topic. Use this command when running in a system’s native shell.

Lists all commands or details for the specified topic. Allows you to search command help by topic.

Displays help text for individual CLI commands. Lists all help text for the specified command. Use this command when running in a system’s native shell.

Displays help text for individual CLI commands. Lists all help text for the specified command.

Display column help (when applicable). See

“Commands with Column Help” (page 43)

for a list of applicable commands.

Displays help text for individual CLI commands. Lists all help text for the specified command.

Commands with Column Help

Column help is provided for some commands to clarify the meaning of each column of data by defining the meaning of the column headers.

Access column help as follows: cli% clihelp –col <command>

When column help is not available, the following message appears:

No help for columns of command “<command>”.

Global Options and Environment Variables 43

Using SSL

The HP 3PAR OS provides a Secure Sockets Layer (SSL) protocol for secure transfer of data between the CLI client and system, and is set with either of the following:

•

The TPDSOCKSSL environment variable.

•

The -sockssl global option.

NOTE: This is the default behavior. TPDSOCKSSL and -sockssl are present for compatibility.

The -nosockssl option overrides this behavior.

The HP 3PAR CLI uses port number 5783 for secure communications and port 5782 for unsecured communications. When the TPDSOCKSSL environment variable or -sockssl global option is set, the socket port defaults to 5783.

Setting the TPDSOCKSSL Environment Variable on Solaris and Linux

To set the TPDSOCKSSL environment variable in Solaris and Linux, see the following system output example:

$ TPDSOCKSSL=1

$ export TPDSOCKSSL

$ cli

Setting the TPDSOCKSSL Environment Variable on Windows

To set the TPDSOCKSSL environment variable in Windows:

On the taskbar, click the Start

→Settings→Control Panel.

In Control Panel, double-click the System icon.

In the System Properties dialog box, click the Advanced tab.

Click Environment Variables.

Enter TPDSOCKSSL in the Variable box.

Enter 1 in the Value box.

Click OK.

Using the -sockssl Option

A secure CLI connection is also available for single instances of a command. On the command line, enter –sockssl following the command name. See the following output example:

$ createuser –sockssl

Setting the CLI Client Network Port

The HP 3PAR CLI client attempts to communicate with the CLI server on the system TCP port number

5783 for secure communications, and on port number 5782 for unsecure communications. The default port used for data transfer is port 5782. If you wish to use another port for data transfer, you can manually set the port that the CLI client will attempt to connect to as follows:

% cli -tpdportnum <port_number>

In the example above, replace <port_number> with the port number you wish to use.

44 Running the HP 3PAR Command Line Interface

Setting the TPDSYSNAME Environment Variable

By setting the system name, you are not prompted for your system name, user name, and password when running the CLI, which can be useful for scripting.

You can specify the system name in the following three ways:

•

Set the TPDSYSNAME environment variable.

•

Use the –sys command line global option.

•

Enter the system name when prompted.

Setting the TPDSYSNAME Environment Variable on Solaris and Linux

To set the environment variable on Solaris or Linux, see the following system output example.

Substitute your system name for <sysname> and use the correct syntax for your shell.

$ TPDSYSNAME=<sysname>

$ export TPDSYSNAME

$ cli

Setting the TPDSYSNAME Environment Variable on Windows

•

To set the environment variable in Microsoft Windows for one instance of a Command Prompt window, run set TPDSYSNAME=<sysname>. Substitute <sysname> with the name of your system. The environment variable remains in effect for that window until you exit that window.

•

To set the environment variable in Windows indefinitely and for all newly created Command

Prompt windows:

Perform

Step 1

through

Step 4

of the procedure for setting the TPDSOCKSSL environment variable in Windows as described in

“Using SSL” (page 44) .

In the Environment Variable dialog box, enter TPDSYSNAME in the Variable box.

Enter your system name in the Value box.

Click OK.

Using the -sys Option

The global option –sys (system) overrides any setting of the environment variable TPDSYSNAME.

On the command line, enter –sys after the command name, followed by your system name. See the following output example. Substitute your system name for <system1>.

$ showhost –sys <system1>

Using the System Name

The system prompts for the system name if the environment variable TPDSYSNAME is not set and the –sys option is not used. To use the system name, see the following output example. Substitute your system name for <system1>.

$ cli system: <system1>

Global Options and Environment Variables 45

Setting Your Name and Password

Your name and password can be provided when prompted, or read from a file that is specified with the environment variable TPDPWFILE or the global option –pwf (password file).

CAUTION: By setting the system name, user name, and password using environment variables, you are not prompted for this information when running the CLI, which can be useful for scripting.

However, passwords must be kept secure. Using encrypted passwords in scripts, using an encrypted pwfile, or the encrypted password on the command line raises the risk of password exposure. It is imperative that the script, pwfile, or command line history file be strictly maintained to avoid compromise of the encrypted password. Failure to do so can leave the user open to impersonation by anyone with access to the encrypted string.

NOTE: LDAP users can save password files using the setpassword command. However, LDAP users are limited to accessing only the system they were logged in to when they saved their password.

The password file has a single line with your name and an encrypted six character minimum password separated by a space. For example:

3paruser PPTpdJPDHuwnU

Additionally, you can also store your password using the setpassword command. Storing your password is useful when you need to:

•

Establish sessions when using the individual commands. Otherwise, you are prompted for user and password information each time you issue a command.

•

Allow unattended operations such as scheduled automatic tasks on the host.

Using the setpassword Command

To store a password on your system, issue the setpassword command to create a password file as displayed in the following example. Substitute a valid password file for <filename>.

$ setpassword –saveonly –file <filename>

See the HP 3PAR Command Line Interface Reference for additional information about the setpassword command.

After the file is written, use either the –pwf global option or TPDPWFILE environment variable to reference the stored password file.

Setting the TPDPWFILE Environment Variable

To reference a password stored using the TPDPWFILE environment variable, see the following example:

$ TPDPWFILE=~/my–pwfile

$ export TPDPWFILE

Using the -pwf Option

To reference a stored password using the –pwf global option, see the following example:

$ showsysmgr –pwf ~/my–pwfile

46 Running the HP 3PAR Command Line Interface

Use of the –pwf option overrides the use of the TPDPWFILE environment variable.

CAUTION: The file containing the user's encrypted password must be protected from unwanted access.

Using the -password Option

You can also specify an encrypted password using the -password <encrypted_password> global option. Use of this option overrides the use of the -pwf global option.

CAUTION: The file containing the user's encrypted password must be protected from unwanted access.

Setting a Password for Multiple HP 3PAR Storage Arrays

Use the createuser command to set the password. The following example displays the successful creation of a new user user1 with the clear-text password 123456, with access to all service pools, and with edit level authority:

$ createuser –c 123456 user1 testdomain edit

User created

Next, use the setpassword -saveonly command to set the encrypted password on the client.

The following example shows how to set the user’s (user1) password on the client:

$ setpassword –saveonly –file <insertfile> user1

Finally, use the createuser -e command to enter the encrypted password.

$ createuser –e user1 testdomain edit

User created

Caching Client Bytecode

Client bytecode contains the majority of functionality of the HP 3PAR CLI and is version specific.

The CLI caches the code required for communication for each different version of the HP 3PAR OS running on the system. The TPDCACHEDIR environment variable controls the location of the cache directory used by the CLI to determine the version of the HP 3PAR OS running on the system.

The TPDCACHEDIR environment variable is set differently in Solaris and Linux, and Windows.

Setting the TPDCACHEDIR Environment Variable on Solaris and Linux

To set the TPDCACHEDIR environment variable in Solaris and Linux, see the following system output example. Substitute the name of your cache directory for cache1 and use the correct syntax for your shell.

$ TPDCACHEDIR=cache1

$ export TPDCACHEDIR

$ cli

Setting the TPDCACHEDIR Environment Variable on Windows

To set the TPDCAHCEDIR environment variable in Windows:

Perform

Step 1

through

Step 4

of the procedure for setting the TPDSOCKSSL environment variable in Windows as described in

“Using SSL” (page 44) .

Global Options and Environment Variables 47

In the Environment Variable dialog box, enter TPDCACHEDIR in the Variable box.

Enter the cache directory name in the Value box.

Click OK.

Startup Files

Startup files can be used to load user-defined procedures and commands. Setting the TPDSTARTFILE environment variable causes the CLI to use a specific startup file when starting the CLI.

The TPDSTARTFILE environment variable is set differently in Solaris and Linux, and Windows.

Setting the TPDSTARTFILE Environment Variable on Solaris and Linux

To set the TPDSTARTFILE environment variable in Solaris and Linux, see the following system output example. Substitute the name of your startup file for <startfile1> and use the correct syntax for your shell.

$ TPDSTARTFILE=<startfile1>

$ export TPDSTARTFILE

$ cli

Setting the TPDSTARTFILE Environment Variable on Windows

To set the TPDSTARTFILE environment variable in Windows:

Perform

Step 1

through

Step 4

of the procedure for setting the TPDSOCKSSL environment variable in Windows as described in

“Using SSL” (page 44) .

In the Environment Variable dialog box, enter TPDSTARTFILE in the Variable box.

Enter the startup file name in the Value box.

Click OK.

Comma Separated Values

HP 3PAR CLI output can be configured to display comma separated values so that data can be easily input into spreadsheets. To set the output display, use:

•

The -csvtable global option.

•

The TPDCSVTABLE environment variable.

•

The setclienv csvtable command (if changing within the Tcl shell; see the HP 3PAR

Command Line Interface Reference for details about this command).

Once set, data is displayed as shown in the following example: cli% showvv -csvtable

,,,,,,,,---Rsvd(MB)---,,,-(MB)-

Id,Name,Prov,Type,CopyOf,BsId,Rd,-Detailed_State-,Adm,Snp,Usr,VSize

0,admin,full,base,---,0,RW,normal,0,0,10240,10240

1,par,full,base,VV_01,1,RW,normal,128,512,16384,256

2,copy,cpvv,vcopy,VV_02,2,RW,normal,0,0,16384,5120

3,vvcp.1.2,tpvv,base,par,1,RO,normal,--,--,16384,10240

4,tpvv,full,base,VV_03,4,RW,normal,128,512,65536,10240

---------------------------------------------------------------------------------

5,total,,,,,,,256,1024,43008,36096

48 Running the HP 3PAR Command Line Interface

Setting the TPDCSVTABLE Environment Variable on Solaris and Linux

To set the TPDCSVTABLE environment variable in Solaris and Linux, see the following system output example:

$ TPDCSVTABLE=1

$ export TPDCSVTABLE

$ cli

Setting the TPDCSVTABLE Environment Variable on Windows

To set the TPDCSVTABLE environment variable in Windows:

Perform

Step 1

through

Step 4

of the procedure for setting the TPDSOCKSSL environment variable in Windows as described in

“Using SSL” (page 44) .

In the Environment Variable dialog box, enter TPDCSVTABLE in the Variable box.

Enter 1 in the Value box.

Click OK.

Using the -csvtable Option

To set the -csvtable global option, see the following example:

$ cli -csvtable

Listing Domains

If you are using HP 3PAR Virtual Domains, you can configure data output to display a domain column. You can configure the output by using the following:

•

The -listdom global option.

•

The TPDLISTDOM environment variable.

•

The setclienv-listdom command (if changing within the Tcl shell; for details about this command, see the HP 3PAR Command Line Interface Reference).

The following example displays CLI output with and without the domain column:

CLI% showvv -listdom

---Rsvd(MB)--- -(MB)-

Id Name Domain Prov Type CopyOf BsId Rd -Detailed_State- Adm Snp Usr VSize_MB

0 admin Dom001 full base --- 0 RW normal 0 0 10240 10240

...

30 V3 - full base --- 30 RW normal 96 256 1024 1024

31 V3.ro - snp vcopy V3 30 RO normal -- -- -- 1024

29 VV5 - full base --- 29 RW normal 96 256 1024 1024

32 VV5.ro - snp vcopy VV5 29 RO normal -- -- -- 1024

17 VV_TeamCPG_1 Dom001 full base --- 17 RW normal 0 0 2048 2048

18 VV_TeamCPG_2 Dom001 full base --- 18 RW normal 0 0 2048 2048

8 vvfromcpg2.0 Dom001 full base --- 8 RW normal 0 0 2048 2048

9 vvfromcpg2.1 Dom001 full base --- 9 RW normal 0 0 2048 2048

---------------------------------------------------------------------------------------

22 total 960 1536 42752 48896

NOTE: If you previously did not use domains and have pre-existing scripts in place, you may not wish to configure your output to display domains because your scripts may be adversely affected.

Global Options and Environment Variables 49

Setting the TPDLISTDOM Environment Variable on Solaris and Linux

To set the TPDLISTDOM environment variable in Solaris and Linux, see the following system output example:

$ TPDLISTDOM=1

$ export TPDLISTDOM

$ cli

Setting the TPDLISTDOM Environment Variable on Windows

To set the TPDLISTDOM environment variable in Windows:

Perform

Step 1

through

Step 4

of the procedure for setting the TPDSOCKSSL environment variable in Windows as described in

“Using SSL” (page 44) .

In the Environment Variable dialog box, enter TPDLISTDOM in the Variable box.

Enter 1 in the Value box.

Click OK.

Using the -listdom Option

To set the -listdom global option, see the following example:

$ cli -listdom

Table Headers and Totals

HP 3PAR CLI output can be configured to either display or not display column headings and totals.

If you are using scripts, you may want to set the CLI output to omit the display of headings and totals to facilitate parsing by your scripts. Options and environment variables including “no” indicate that headings and totals are not displayed. To set the output display, use:

•

The -nohdtot or -hafter global options.

•

The TPDNOHDTOT or TPDHAFTER environment variables.

•

The setclienv -nohdtot or setclienv -hafter commands (if changing within the

Tcl shell; for details about this command, see the HP 3PAR Command Line Interface Reference)).

The following example displays CLI output with and without column headings and totals:

showvv -nohdtot

0 admin Dom001 full base --- 0 RW normal 0 0 10240 10240

...

30 V3 - full base --- 30 RW normal 96 256 1024 1024

31 V3.ro - snp vcopy V3 30 RO normal -- -- -- 1024

29 VV5 - full base --- 29 RW normal 96 256 1024 1024

32 VV5.ro - snp vcopy VV5 29 RO normal -- -- -- 1024

17 VV_TechPubs_1 Dom001 full base --- 17 RW normal 0 0 2048 2048

18 VV_TechPubs_2 Dom001 full base --- 18 RW normal 0 0 2048 2048

8 vvfromcpg2.0 Dom001 full base --- 8 RW normal 0 0 2048 2048

9 vvfromcpg2.1 Dom001 full base --- 9 RW normal 0 0 2048 2048

Setting the Environment Variable on Solaris and Linux

$ TPDNOHDTOT=1

$ export TPDNOHDTOT

$ cli

Substitute TPDHAFTER for TPDNOHDTOT in the example above, as necessary.

50 Running the HP 3PAR Command Line Interface

Setting the Environment Variable on Windows

To set the TPDNOHDTOT or TPDHAFTER environment variable in Windows:

Perform

Step 1

through

Step 4

of the procedure for setting the TPDSOCKSSL environment variable in Windows as described in

“Using SSL” (page 44) .

In the Environment Variable dialog box, enter TPDNOHDTOT or TPDHAFTER in the Variable box.

Enter 1 in the Value box.

Click OK.

Using the -nohdtot Option

To set the -nohdtot global option, see the following example:

$ cli -nohdtot

Using the -hafter Option

To set the -hafter global option, see the following example:

$ cli -hafter 20

Forcing Commands

A number of CLI commands return confirmation prompts before executing the command operations.

For these commands, an –f option is provided allowing you to bypass the confirmation and force the execution of the command. The TPDFORCE environment variable automatically provides the functionality of the -f option and alleviates the need of having to specify the –f option when issuing commands that would otherwise require a confirmation.

The TPDFORCE environment variable is set differently in Solaris and Linux, and Windows.

Setting the TPDFORCE Environment Variable on Solaris and Linux

To set the TPDFORCE environment variable in Solaris and Linux, see the following system output example:

$ TPDFORCE=1

$ export TPDFORCE

$ cli

Setting the TPDFORCE Environment Variable on Windows

To set the TPDFORCE environment variable in Windows:

Perform

Step 1

through

Step 4

of the procedure for setting the TPDSOCKSSL environment variable in Windows, as described in

“Using SSL” (page 44) .

Enter TPDFORCE in the Variable box.

Enter 1 in the Value box.

Click OK.

Global Options and Environment Variables 51

Stand-alone Commands

There are two ways to issue CLI commands from a shell prompt in Solaris and Linux, or from a

Windows command prompt:

•

CLI commands can be executed like typical UNIX and MS-DOS commands.

◦

If the CLI commands are run as individual commands, you are prompted for your user name and password for each command. This can be avoided by setting your system to read your user name and password from a file. See

“Setting Your Name and Password”

(page 46)

for more information.

◦

If you are running the CLI commands as individual commands, you can put each command in a script or pipe them to other commands. You can use the shell of your choice for scripting or for initiating interactive sessions that provide history and line editing capabilities.

•

Enter cli at the DOS or Solaris or Linux prompt to run the cli program. Running this progrm places you into an interactive Tcl shell where all CLI commands are available.

◦

The Tcl shell connects to the system and remains connected until you exit from the shell.

While the Tcl shell is connected, you are not prompted for your user name and password for each command you issue.

◦

The Tcl shell provides access to the Tcl language that allows you to write Tcl procedures or source Tcl scripts that build on top of CLI commands.

NOTE: Help is available to display information about CLI commands. If you started the CLI with the cli command, you can obtain help by typing either help or clihelp. When you run individual CLI commands from a system's native shell, use clihelp.

For details about HP 3PAR CLI commands, see also the HP 3PAR Command Line Interface Reference.

SSH

The system is provided with Secure Shell (SSH) protocol version 2 that enables great flexibility in accessing the HP 3PAR CLI and provides an alternative to installing the remote CLI client. SSH uses public-private key encryption algorithms to encrypt all traffic between the client and server, including passwords.

SSH client applications are typically provided with the following operating systems:

•

AIX

•

HP–UX

•

Linux

•

Oracle® Solaris™

For Microsoft® Windows® users, an SSH client is available at http://www.openssh.org

Benefits of Using SSH

SSH provides the following benefits:

•

No HP 3PAR CLI installation. CLI clients are not required to access and use the CLI (assuming

SSH client is installed).

•

No version matching. The HP 3PAR CLI and HP 3PAR OS versions do not need to match because the CLI does not need to be installed remotely.

•

Strong encryption. All information exchanged between client machines and systems are encrypted.

52 Running the HP 3PAR Command Line Interface

•

Data integrity. Integrity checking is executed to verify that data has not been altered during transmission from sender to receiver.

•

Server authentication. The system can be authenticated using the public key authentication scheme. The system’s public key can be stored on client machines, allowing the SSH client to compare the key presented by the system to the key stored on the client machine.

CLI User Name Restrictions Using SSH

There are several CLI user names that are reserved for use by HP. Reserved names are as follows:

• root

• daemon

• bin

• console

• nobody

• sshd

• telnetd

• sys

• sync

• man

• proxy

• list

New Users

When creating a new user, specify a new user name that is not on the reserved name list.

Existing Users

To delete a user, issue the removeuser command.

cli% removeuser pw1

User removed

In the previous example, a user with the reserved user name of pw1 is removed.

To create a new user, issue the createuser command.

cli% createuser ROOT1 all edit

In the previous example, new user ROOT1 is created.

See the HP 3PAR Command Line Interface Reference for complete information about these commands.

Accessing the CLI Using SSH

NOTE: The following screen examples display output for UNIX systems. Windows screens are identical, with DOS prompts replacing UNIX prompts.

A total of 16 connections are allowed at one time.

To access the CLI using SSH:

SSH 53

From any host that is running SSH client, enter the following example:

$ ssh user@<System–host–name>

In the previous example, ssh user is the first default user with Super rights and

<System–host–name> is the array host name.

If this is the first login from the client host (for example, when the host does not already have a system public key for identity), expect the following message:

The authenticity of host <System–host–name> can’t be established.

RSA key fingerprint is 68:a6:c9:60:a1:cb:….

Are you sure you want to continue connecting (yes/no): yes

When prompted to continue, enter yes.

This is normal SSH behavior, because the client host does not have the system’s public key.

If the system’s public key has previously been stored on the client host, this message will not be displayed. After you have set the key, this message will not be displayed.

NOTE: The validity of the key fingerprint presented at this point can be verified by using the public keys provided as part of the HP 3PAR Administration Tools. These keys can be installed with the administration tools or can be obtained directly from the HP 3PAR Administration

Tools CD. Consult the SSH client documentation for instructions on creating a key fingerprint from the public key.

When prompted, enter the default password. If you do not have the password, contact your service provider.

After you enter the password, the CLI prompt appears.

<System–host–name> cli %

In the previous example, System–host–name is the system’s cluster name or host name.

You are now in the CLI shell and can issue the CLI commands that are documented in this manual.

If you need to create additional CLI users, use the createuser command. For more information, see

“Creating Users” (page 18)

Terminate the CLI session by typing exit at the prompt.

<System–host–name> cli % exit

Newly created CLI users can access the CLI by following these instructions, while substituting their own user name, system name, and password when prompted.

CLI Scripting Through SSH

You can use SSH public key authentication to issue CLI commands in scripts. No password is required; however, you will need to generate a public/private key pair.

54 Running the HP 3PAR Command Line Interface

CAUTION: For security purposes, the file containing the private key must be protected from unauthorized access. Failure to protect the file can cause the key to be compromised.

CAUTION: If the system is operating in Common Criteria mode, LDAP users must not use a public key. For more information about Common Criteria, see the HP 3PAR Common Criteria

Administrator’s Reference.

•

The public key must be stored on the system using the setsshkey command to enable users to log in without a password.

•

The private key must be kept in a file accessible by scripts that use CLI commands.

The key pair is generated by using the ssh–keygen utility (typically included in an SSH client software package and available on UNIX and Windows platforms).

NOTE: The following screen examples show output for UNIX systems. Windows screens are simlar, with DOS prompts replacing UNIX prompts.

The following steps describe setting up CLI scripting through SSH:

Create a CLI user and password using the createuser command.

$ssh user1@system1

3paradm’s password: ****** system1 cli% createuser –c testpw3 user3 all browse

User created

In the previous example, user user1 logs into system system1 and creates user user3 with the password testpw3.

Create a key pair using the ssh–keygen utility. Both rsa and dsa key formats are supported by the system, and the recommended key length is at least 1024 characters.

NOTE: For additional information about the ssh–keygen utility and rsa and dsa key formats, consult the SSH client documentation.

To create a key pair using rsa format:

$ ssh–keygen –b 1024 –t rsa

To create a key pair using dsa format:

$ ssh–keygen –b 1024 –t dsa

Generating public/private dsa key pair.

Enter file in which to save the key (/home/usr/user3/.ssh/id_dsa):

Created directory '/home/usr/user3/.ssh'.

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /home/usr/user3/.ssh/id_dsa.

Your public key has been saved in /home/usr/user3/.ssh/id_dsa.pub.

The key fingerprint is:

3f:a0:b5:6a:4d:dd:45:76:37:fb:a3:3e:52:44:55:32 [email protected]

SSH 55

The ssh–keygen utility generates two files: id_rsa.pub and id_rsa.pub (or id_dsa.pub

and id_dsa.pub).

•

Generate the key with or without a pass phrase.

◦

When the key is generated with a pass phrase, your private key is encrypted and stored in the file.

NOTE: The pass phrase must be entered and the private key decrypted before a script is run. To decrypt the private key, run the ssh–agent and ssh–add commands

(see

Step 6 ).

◦

When a pass phrase is not specified, the key is stored unencrypted in the file.

•

Ensure that only the owner has access and read/write permission on the private key file, otherwise the SSH client refuses the key file.

$ssh user3@system1 user3@system1’s password: testpw3

Issue the setsshkey command.

system1 cli% setsshkey setsshkey

Please enter the SSH public key below. When finished, press enter twice. The key is usually long. It's better to copy it from inside an editor and paste it here. (Please make sure there is no extra blanks.) ssh–rsa AF5afPdciUTJ0PYzB6msRxFrCuDSqDwPshqWS5tGCFSoSZdE= user3’s pubic key

SSH public key successfully set!

Write your script. See the following example:

#!/bin/sh

# Assume that the user name “user3” exists on system1

# The private key file “id_rsa” is accessible.

SSH="ssh –i id_rsa –l user3 system1 "

# Execute the command passed in as command line argument $1

${SSH} $1

56 Running the HP 3PAR Command Line Interface

If you specified a pass phrase when creating the key pair, run ssh-agent and ssh-add to decrypt the key before running your script (<script_name> in the following example).

$ ssh–agent echo Agent pid 24216

$ ssh–add

Enter passphrase for /home/usr/user3/.ssh/id_dsa: ******

Identity added: /home/usr/user3/.ssh/id_dsa (/home/usr/user3/.ssh/id_dsa)

$ <script_name>

NOTE: You can redirect the standard input, or stdin, to execute multiple CLI commands.

SSH 57

4 Managing HP 3PAR Virtual Domains

Overview

HP 3PAR Virtual Domains Software (domains) enables an administrator to create multiple domains, or spaces, within a system, where each domain is dedicated to a specific application. In effect, using domains restricts users to a subset of the volumes and hosts in a system, and prevents users from exporting virtual volumes to hosts outside of the users’ assigned domains. For more information about domains, see the HP 3PAR StoreServ Storage Concepts Guide. This chapter provides instructions on creating domains and describes the administration tasks associated with maintaining domains.

NOTE: HP 3PAR Virtual Domains Software requires an HP 3PAR Virtual Domains Software license.

Contact your local service provider for details.

Default Domains

An HP 3PAR CLI user’s default domain is the domain that the user accesses at the start of each CLI session. For example, if a user has Edit rights to Domains A and B and the default domain has been set to Domain A, each time a user starts a new CLI session, only objects in Domain A can

be viewed and worked with ( Figure 1 (page 58) ). The user’s default domain can be set and reset

at any time by the administrator.

In the following example, the default domain (Domain A) can be reassigned to Domain B for the current working session using the setclienv currentdomain <name> command. When the currentdomain <name> is set, you are able to view and work on objects in Domain B for a single CLI session. When that session is over, your next session is started in your default domain

(Domain A) (see

Figure 1 (page 58)

). Thus, a current domain refers to the domain in which you are working during a particular, single CLI session.

Figure 1 Assigned Default and Current Domains

Creating a Domain

To create a domain, issue the createdomain <domain_name> command, where

<domain_name> is the name you want to assign the domain. The <domain_name> can be a maximum of 31 characters in length.

If you want to add an informational note to a domain during its creation, issue the createdomain

-comment <comment> <domain_name> command, where <comment> is the text of the note you wish to add about the domain being created. The comment length is restricted to 511 characters.

•

You can create up to 1,024 domains within a single system.

•

You can specify the maximum retention time for a virtual volume in the domain with the-vvretentiontimemax option.

58 Managing HP 3PAR Virtual Domains

For a complete list of options available for the createdomainset command, see the HP 3PAR

Command Line Interface Reference and HP 3PAR CLI Help. For additional information about domains, see the HP 3PAR StoreServ Storage Concepts Guide.

Viewing Domains

From time to time, you may wish to view the domains in your system. Additionally, when managing your domain objects as described in

“Managing Domain Objects” (page 60)

, you may need to view the objects’ domain associations.

To view the domains in your system, issue the showdomain -d command. For details about the showdomain command, see the HP 3PAR Command Line Interface Reference.

NOTE: To set your system output to display domain information, you must first set the TPDLISTDOM environment variable, the -listdom global option, or if you are working in a Tcl shell, issue the setclienv listdom 1 command. See

“Listing Domains” (page 49)

for further information.

To view a system object’s domain association, issue the showhost, showvv, or showcpg commands.

Modifying a Domain

For any existing domain, you can change the domain’s name or add comments to that domain using the setdomain command. For details about the setdomain command, see the HP 3PAR

Command Line Interface Reference.

Changing a Domain Name

To change a domain’s name, issue the setdomain -name <name> <domain_name> command, where:

•

<name> is the new name you wish to assign the domain.

•

<domain_name> is the current name of the domain you are renaming.

Once changed, users and comments previously belonging to the old domain name are displayed as belonging to the new domain name. All previous associations, objects, and settings (such as default settings) are also transferred.

Adding Comments to a Domain

If a comment was not added to a domain during its creation and you wish to add a note to that domain, issue the setdomain -comment <comment> <domain_name> command, where:

•

<comment> is the comment you are adding to the specified domain.

•

<domain_name> is the name of the domain to which you are adding a comment.

The comment length is restricted to 511 characters and the comment text must be enclosed in quotation marks.

Removing a Domain

Prior to removing a domain, any users belonging to that domain must be removed (see

“Removing

Users From a Domain” (page 20) ) and assigned to another domain, or must be removed completely

(see

“Adding Users to a Domain” (page 20) ). Any objects belonging to the domain must be removed

form the domain, or moved to another domain before removing the domain. Domain objects include virtual volumes, common provisioning groups (CPGs), and hosts.

To remove a domain, issue the removedomain <domain_name> command, where

<domain_name> is the domain you want to delete.

Viewing Domains 59

Managing Domain Objects

Domain objects can be moved in and out of a domain, or have their domain associations entirely removed. In doing so, all objects related either directly or indirectly to the domain object being managed are also moved or removed. These relationships include, but are not limited to, VLUNs between hosts and VVs, VVs which are drawing from CPGs and multiple VVs sharing the same

LD. In order to move or remove a domain object or domain association, you must have Super or

Edit user rights with access to all domains.

NOTE: Before proceeding with any domain management activities, you may want to view the domain associations for your system objects as described in

“Viewing Domains” (page 59) .

Moving Domain Objects to Another Domain

To move a domain object in or out of a domain, issue the movetodomain -vv|-cpg|-host

<object_name><domain_name>|set:<set_name> command, where:

•

-vv|-cpg|-host is the type of object (VV, CPG, host, respectively) you are moving.

•

<object_name> is the name of the VV, CPG, or host you are moving.

•

<domain_name> is the name of the domain to which you are moving the specified object.

•

<set_name> is the name of the domain set to which you are moving the specified host.

NOTE: If a CPG or VV in a CPG is part of an Adaptive Optimization configuration (aocfg), then if the VV or CPG is specified as the target of a movetodomain command, all CPGs and related

VVs in the aocfg will also be moved to the target domain.

Removing the Domain Association from a Domain Object

To remove the domain association from a domain object, issue the movetodomain

-vv|-cpg|-host <object_name> -unset command, where:

•

-vv|-cpg|-host is the type of object (VV, CPG, host, respectively) from which you are removing the domain association.

•

<object_name> is the name of the VV, CPG, or host from which you are removing the domain association.

Managing Virtual Domain Autonomic Groups

Virtual domains can be combined into autonomic groups. A autonomic groups are sets of objects that can be managed as one object. If you have a group of domains that require the same administrative procedures, it is easier to group those domains into a set and manage them together.

For example, you can create a domain set and put all of the hosts in a cluster into a host set. By setting the domain of the hosts in the host set to the newly created domain set, all the virtual volumes exported to one host in the cluster are accessible to all the hosts in the cluster. If one of the hosts in the cluster is a backup host, all of the virtual volumes in the domain set can access the backup host. Without domain sets there is no way for a host to access volumes from different domains at the same time. Individual domains can be members of multiple domain sets.

Hosts are the only objects that can be members of a domain set. All other objects can only belong to a single domain. If a host that is a member of a domain set is moved with the movetodomain command to an individual domain, then all objects associated with the host must be members of the destination domain or the command will fail. Moving a host to a domain set does not change the domain of any objects associated with the host. If a volume is exported to a host that is a member of a domain set that is selected directly or indirectly by the movetodomain command, and if the domain set includes the destination domain of the volume, the move does not propagate to the host or any of the volumes exported to the host.

60 Managing HP 3PAR Virtual Domains

Virtual domains added to a set inherit the rights of that set. Any action that requires Browse rights for a host requires the user to have Browse rights in any domain in the domain set. Any action that requires Edit rights for the host requires the user to have Edit rights in all domains in the domain group.

A virtual domain in a virtual domain set cannot be removed from the system until it has been removed from the virtual domain set, or until the virtual domain set is removed from the system.

Removing a virtual domain set does not remove the virtual domains in that set. Changing the name of a virtual domain in a set does not change the rights of the virtual domain or remove it from the virtual domain set.

Creating Virtual Domain Sets

To create a domain set, issue the createdomainset <set_name> <domain_names> command, where:

•

<set_name> is the name of the domain set being created.

•

<domain_names> are the names of the domains included in the domain set.

For a complete list of options available for the createdomainset command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Adding Virtual Domains to Virtual Domain Sets

To add a domain to an existing domain set, issue the createdomainset -add <set_name>

<domain_names> command, where:

•

<set_name> is the name of the domain set that will include the added domains.

•

<domain_names> are the names of the domains being added to the domain set.

For a complete list of options available for the createdomainset command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Modifying Virtual Domain Sets

To change the name of a domain set, issue the setdomainset -name <new_name>

<set_name> command, where:

•

<new_name> is the new name of the domain set.

•

<set_name> is the name of the domain set being modified.

For a complete list of options available for the setdomainset command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Removing Virtual Domain Sets

To remove a domain set from the system, or to remove domains from a set, issue the removedomainset <set_name> <domain_names> command, where:

•

<set_name> is the name of the virtual volume set being removed or modified.

•

<domain_names> are the names of the domains being removed from the <set_name> domain set. This specifier is optional if you are removing the entire set.

For a complete list of options available for the removedomainset command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Viewing Virtual Domain Sets

To view all domain sets in the System, issue the showdomainset command.

To view the details of a specific domain, issue the showdomainset -d <domainset_name> command.

Managing Virtual Domain Autonomic Groups 61

To view domain sets containing domains matching a pattern, issue the showdomainset -domain

<pattern>* command.

62 Managing HP 3PAR Virtual Domains

5 Managing Ports and Hosts

Overview

The system sees a host as a set of initiator port World Wide Names (WWNs) or iSCSI Names.

Hosts that are physically connected to ports on the system are automatically detected. The FC port

WWNs and iSCSI port iSCSI Names are displayed in the HP 3PAR CLI. You can also add new

WWNs or iSCSI Names for unestablished host paths and assign them to a host before they are physically connected. These WWNs or iSCSI Names do not need to be associated with target ports on the system controller nodes. This allows for plug-and-play functionality that avoids the need for manual reconfiguration after connecting new hosts.

FCoE connectivity is supported on HP 3PAR StoreServ 10000 Storage systems and HP 3PAR

StoreServ 7000 Storage systems through the use of Converged Network Adapters (CNA). CNA ports can be configured to be used as FCoE or iSCSI ports.

Host personas are a set of behaviors that permit hosts connected to FC or iSCSI ports on the system to deviate from the default host behavior. By assigning a persona to a host, multiple host types that require distinct customized responses can share a single system port. For example, hosts running Windows, Linux, and AIX operating systems can all connect to the same system port. This simplifies connecting hosts to the system and reduces management time related to complex host connections.

For more information about ports, hosts, and host personas, see the HP 3PAR StoreServ Storage

Concepts Guide.

NOTE: See the HP 3PAR Implementation Guides for recommended practices and detailed configuration information about using your specific host devices with the system.

Modifying Port Parameters

Use the HP 3PAR CLI controlport command to modify the FC ports and the Gigabit Ethernet ports used for the HP 3PAR Remote Copy Software over IP (RCIP) solution. Use the controliscsiport command to modify the iSCSI ports on the system. These commands control several aspects of the ports. Whenever you use these commands, you must use a sub-command specifying the operation you want to perform and include the port location.

The HP 3PAR CLI displays the controller node port locations in the following format:

. For example: 2:4:1.

•

Node : Valid node numbers are 0-7, depending on the number of nodes installed in your system. When viewing a system from the rear of a cabinet:

◦

F-Class nodes are numbered 0-3 from top to bottom.

◦

T-Class nodes are numbered 0-7 from left to right, top to bottom.

◦

StoreServ 10000 nodes are numbered 0-7 from left to right, bottom to top.

◦

StoreServ 7000 nodes are numbered 0-1 or 0-3 from bottom to top.

•

Slot : Valid node slot numbers are 0-9, depending on the class of nodes installed in your system.

◦

F-Class slots are numbered 0-5 from left to right.

◦

T-Class slots are numbered 0-7 from left to right.

Overview 63

◦

StoreServ 10000 slots are numbered 0-9 from left to right, bottom to top in a node in the lower chassis. In the upper chassis, slots are numbered 0-9 from left to right, top to bottom.

◦

HP 3PAR StoreServ 7000 Storage systems have one slot per node. Slot 0 is reserved for onboard SAS, slot 1 is reserved for onboard FC, and slot 2 is reserved for the HBA.

•

Port : Valid node port numbers are 1-4 for all Host Bus Adapters (HBA).

◦

F-Class ports are numbered from top to bottom.

◦

T-Class ports are numbered from top to bottom.

◦

StoreServ 10000 ports are numbered from bottom to top in a node in the lower chassis.

In the upper chassis, ports are numbered from top to bottom.

◦

StoreServ 7000 ports are numbered 1-4 from left to right in a node in the lower node enclosure. In the upper node enclosure, slots are numbered 1-4 from right to left.

FC Port Settings

The HP 3PAR CLI controlport command is described in detail in the HP 3PAR StoreServ Storage

Command Line Interface Reference and the HP 3PAR CLI Help. Use the controlport command to perform the following tasks:

•

Set the port mode with the config sub-command followed by disk|host|rcfc, and set the port location in node:slot:port format.

To set the port mode:

Disconnect the cable from the port on the system.

Set the port mode. Issue the controlport config disk|host|rcfc

<Node>:<Slot>:<Port> command.

Reconnect the cable to the port on the system.

•

Set the port data rate in Gbps with the rate sub-command followed by 1, 2 or 4, and the port location in node:slot:port format. Alternatively, you can use the controlport rate auto command, followed by the port location in node:slot:port format, to allow the system to determine the data rate automatically. The default value for this option is auto.

To set the port data rate in Gbps, issue the controlport rate <1|2|4>

<node:slot:port> command.

•

When unique_nwwn is enabled, the port presents a unique node name for the connection.

To set the mode of an FC port, or to set the unique node WWN option for the port, issue thecontrolport config <connmode> [-ct <ctval>] [-unique_nwwn enable|disable] <node:slot:port> command, where:

◦

<connmode> is the one of the following connections: disk|host|rcfc.

◦

<ctval> is either loop or point. The loop parameter sets the port to arbitrated loop mode, and the point parameter sets the port to point-to-point mode.

•

Set the port’s Class 2 service support level with the cl2 sub-command followed by ack0, ack1

, or disable and then by the port location in node:slot:port format.

To set the port’s Class 2 service support level, issue the controlport cl2 <cl2val>

<node:slot:port> command.

•

Set the port’s VLUN Change Notification (VCN) support generation with the vcn sub-command followed by either enable or disable, and the port location in node:slot:port format.

To set the port’s VLUN Change Notification (VCN) support, issue the controlport vcn

<enable|disable> <node:slot:port> command.

64 Managing Ports and Hosts

NOTE: Other options are available for the controlport command, including options for resetting the port’s mode, modifying Remote Copy settings, and issuing an FC Loop Initialization

Primitive (LIP) procedure. These options are described in detail in the HP 3PAR Command Line

Interface Reference and the HP 3PAR CLI Help.

iSCSI Port Settings

The HP 3PAR CLI controliscsiport command is described in detail in the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help. Use the controliscsiport command to perform the following tasks:

•

To set the IP address and netmask of the iSCSI port, use the addr sub-command followed by the IP address and netmask, then the port location in node:slot:port format.

To set the IP address and netmask of the iSCSI port, issue the controliscsiport addr

<IP_address> <netmask> <node:slot:port> command.

•

To set the gateway address of the iSCSI port, use the gw sub-command followed by the gateway address, then the port location in node:slot:port format.

Issue the controliscsiport gw <gw_address> <node:slot:port> command.

•

To set the TCP port number for the iSNS server, use the isnsport sub-command followed by the iSNS server port number, then the port location in node:slot:port format.

To set the TCP port number for the iSNS server, issue the controliscsiport isnsport

<isns_port> <node:slot:port> command.

NOTE: Other options are available for the controliscsiport command, including options for setting the primary and secondary iSNS server IP addresses, and for setting the maximum transmission unit (MTU) size for the iSCSI port. These options are described in detail in the HP

3PAR Command Line Interface Reference and the HP 3PAR CLI Help.

Port Target, Initiator, and Peer Modes

The system controller node ports operate in different modes. Depending on the type of port, the port may operate in target, initiator, or peer mode.

FC ports use the following firmware mode settings:

•

Target mode for ports that connect to hosts and receive commands from those hosts.

•

Initiator mode for ports that connect to the system physical disks and send commands to those disks.

•

Initiator mode for Remote Copy over FC (RCFC).

Port Target, Initiator, and Peer Modes 65

iSCSI ports use the following firmware mode setting:

•

Target mode for ports that connect to hosts and receive commands from those hosts.

Gigabit Ethernet ports use the following firmware mode setting:

•

Peer mode for Ethernet ports, used for Remote Copy over IP (RCIP).

FCoE ports use the following firmware mode setting:

•

Target mode for ports that connect to hosts and receive commands from those hosts.

Use the HP 3PAR CLI showport command to display the current mode for all ports. Use the controlport command to change the mode of an FC port. These commands are described in detail in the HP 3PAR Command Line Interface Reference and the HP 3PAR CLI Help.

CAUTION: Ports in the same FC adapter should be set to the same mode:

•

For dual-port LSI cards, both ports must use the same mode.

•

For quad-port LSI cards, each port pair (ports 1&2 and 3&4) must use the same mode.

•

For QLogic cards, it is strongly recommended that all ports in a card be set to the same mode.

Active and Inactive Hosts

An active host is a host that is connected to a system port and recognized by the HP 3PAR OS.

Under normal operation, an active host may have a number of volumes exported to it and therefore the host has access to those volumes.

An inactive host is a host that is known to the HP 3PAR OS but is not recognized as being connected to any system port at the moment. This may be because the host is currently disconnected from the system port, or due to an error condition such as link failure, or because the host is offline.

When a host on a system port becomes inactive for any reason, the following happens:

The HP 3PAR OS recognizes that the host is missing on the port and changes the state of the host from active to inactive.

The HP 3PAR OS remembers all volumes exported to the host before it became inactive.

It will not unexport the volumes on the port with the missing host.

If and when the host reappears on the same port, the HP 3PAR OS will change the state of the host to active again. At that time, the host will again have access to all previously exported volumes.

Managing Hosts

The system sees a host as a set of initiator port WWNs or iSCSI Names. The HP 3PAR OS administration tools allow you to create, modify, and remove FC and iSCSI host paths and their properties. When creating a new host, you can either create a host with or without assigning

WWNs or iSCSI Names. A virtual volume that is exported to a host is exported to all the WWNs that make up the host. If you need to export virtual volumes to particular host computer WWNs or iSCSI Names, you can create separate hosts on the system and assign each WWN or iSCSI Name to its own host. The host management commands are described in detail in the HP 3PAR StoreServ

Storage Command Line Interface Reference and the HP 3PAR CLI Help.

Host Management CLI Commands

Use the following CLI commands to manage hosts and host paths:

• showhost

—display information about defined hosts and host paths in the system.

• createhost

—create a host or add paths to host.

• createhostset

—create a host set or add a host to an existing host set.

• sethost

—modify properties of existing hosts.

66 Managing Ports and Hosts

• sethostset

—change the name of a host set.

• removehost

—remove a system host or paths to a host.

• removehostset

—remove a host set from the system, or remove hosts from a set.

• servicehost

—execute removal and replacement actions for a host.

Creating Hosts

When you create a new host, you are defining the characteristics of a new host path from the system to the host. Defining host characteristics includes the assignment of a name to a host, and the assignment of a path to that host. Two types of host paths can be assigned: FC or iSCSI paths.

You should create multiple paths to each host.

In addition to assigning FC or iSCSI paths when creating a host, you can also annotate the host with descriptive information such as the host’s location, IP address, operating system, model, and owner, using either the createhost or sethost commands. This information is for annotation purposes only and it does not affect the operation of the system. See the HP 3PAR Command Line

Interface Reference or the HP 3PAR CLI Help for further information.

NOTE: There should be at least two paths to each host to facilitate updates to the system. Failure to create at least two host paths may result in unnecessary system downtime.

See the HP 3PAR Implementation Guide for recommended practices and detailed configuration information about using specific host devices with the system.

Creating a Host with a Fibre Channel Path

To create a host with an FC path:

Determine the HBA’s WWN by issuing the showhost command.

Issue the createhost -persona <persona_number> <host_name> <WWN> command, where:

•

<persona_number> is the host persona number assigned to the host.

•

<host_name> is the user-designated name of the host being defined.

•

<WWN> is the HBA’s WWN.

If the Host Explorer agent is running on the host, the createhost <host_name> command automatically creates a host with the path information received from the Host Explorer agent.

Creating a Host with an iSCSI Path

To create a host with an iSCSI path:

Determine the HBA’s iSCSI Name by issuing the showport -iscsiname command.

Issue the createhost -iscsi -persona <persona_number> <host_name>

<iSCSI_name> command, where:

•

<persona_number> is the host persona number assigned to the host.

•

<host_name> is the user-designated name of the host being defined.

•

<iSCSI_Name> is the host iSCSI Name, as determined from step 1 above.

If the Host Explorer agent is running on the host, the createhost -iscsi <host_name> command automatically creates a host with the path information received from the Host Explorer agent.

Creating a Host without Assigning a Path

In instances where the HBA’s FC WWN or iSCSI name is unavailable, you can create a host as a placeholder until the path information becomes available. If the Host Explorer agent is not running

Creating Hosts 67

on the host, the createhost <host_name> command creates a host without any path information. If the Host Explorer agent is running on the host, the createhost <host_name> command automatically creates a host with the path information received from the Host Explorer agent.

The host path information is required to display the device name. If the path information is not reported from the host to the system, then the device name appears as Unknown.

Issue the createhost <host_name> command, where <host_name> is the user-designated name of the host being defined.

Modifying Hosts

You can modify the following parameters and functions of an existing host:

•

Change the host’s name.

•

Add or remove WWNs or iSCSI Names.

•

Add or remove iSCSI CHAP authentication information.

The following CLI commands are described in detail in the HP 3PAR Command Line Interface

Reference and the HP 3PAR CLI Help.

Changing a Host Name

To change a host name, issue the sethost -name <new_host_name> <host_name> command, where:

•

<new_host_name> is the new name you wish to assign to the existing host.

•

<host_name> is the original name of the host you are modifying.

Adding Fibre Channel Path WWNs

To add a WWN to an existing host:

Determine the HBA’s WWN by issuing the showhost command.

Issue the createhost -add <host_name> <WWN> command, where:

•

<host_name> is the name of the host being modified.

•

<WWN> is the HBA’s WWN.

Repeat as necessary for any additional WWNs you wish to add to the host definition.

Adding iSCSI Path iSCSI Names

To add an additional iSCSI Name for an existing host:

Determine the HBA’s iSCSI Name by issuing the showport -iscsiname command.

Issue the createhost -add -iscsi <host_name> <iSCSI_name> command, where:

•

<host_name> is the name of the host being modified.

•

<iSCSI_Name> is the host iSCSI Name as determined from step 1 above.

Repeat as necessary for any additional iSCSI Names you wish to add to the host definition.

Removing Fibre Channel Path WWNs

To remove a WWN from an existing host, issue the removehost <host_name> <WWN> command, where:

•

<host_name> is the name of the host being modified.

•

<WWN> is the FC path being removed.

68 Managing Ports and Hosts

Removing iSCSI Path iSCSI Names

To remove an iSCSI Name from an existing host, issue the removehost -iscsi <host_name>

<iSCSI_name> command, where:

•

<host_name> is the name of the host being modified.

•

<iSCSI_name> is the iSCSI path being removed.

Configuring iSCSI CHAP Authentication Information

A host with an iSCSI path can be modified as an initiator or target with iSCSI CHAP authentication information. You cannot set the target CHAP authentication information before setting the initiator

CHAP authentication information.

•

To configure a host as a CHAP initiator, issue the sethost initchap <secret>

<host_name> command.

•

To configure a host as a CHAP target, issue the sethost targetchap <secret>

<host_name> command.

For both commands listed above, <secret> is the user-defined security key and <host_name> is the name of the host you are modifying.

During configuration, you can also optionally set the CHAP name and set the CHAP secret as a hexadecimal number. See the HP 3PAR Command Line Interface Reference for further information.

Removing iSCSI CHAP Authentication Information

To remove CHAP authentication information from a host with an iSCSI path, issue one of the following commands:

• sethost removechap -target <host_name>

• sethost removechap <host_name>

For both commands listed above:

◦

<host_name> is the name of the host you are modifying.

◦

The -target argument is specified for removal of target CHAP authentication only.

Moving, Removing, and Disconnecting Hosts

Use the following commands to display active hosts and the volumes exported to the hosts:

• showhost

• showvlun

To display inactive hosts and the volumes that were exported to the hosts, use the servicehost list command.

The showhost, showvlun, and servicehost CLI commands are described in detail in the HP

3PAR Command Line Interface Reference and the HP 3PAR CLI Help.

After you move a host to a new port, you must:

•

Remove the old host definitions.

•

Disconnect the host from the system.

•

Connect the host to the new port.

To move the host to another system port, you must do the following:

Moving, Removing, and Disconnecting Hosts 69

Use the HP 3PAR CLI command servicehost copy to create an inactive host on the system port to which you wish to move the host. The inactive host created with this command is identical to the active host that is to be relocated to this port.

The servicehost copy command automatically exports all volumes that are currently exported to the active host to the new, inactive host once it is created. For more information about active and inactive hosts, see

“Active and Inactive Hosts” (page 66) .

The VLUNs from the specified source port (src_node:slot:port) are copied from the host

WWNs or iSCSI Names matching the specified pattern (WWN_or_iSCSI_name_pattern) to the specified destination port (dest_node:slot:port). If necessary, the port is reset to target mode.

To create an inactive host on the system port to which you wish to move the host, issue the servicehost copy <src_node:slot:port> <WWN_or_iSCSI_name_pattern>

<dest_node:slot:port> command, where:

•

<src_node:slot:port> is the current port location.

•

<WWN_or_iSCSI_name_pattern> specifies that the indicated WWN or iSCSI Name is treated as a glob-style pattern.

•

<dest_node:slot:port> is the destination port location.

Remove the host definitions from the old port or ports.

Removing the host definitions does not remove the old host paths. To remove the host paths, see

“Removing Host Paths” (page 70) . To remove host definitions and all VLUNs associated

with the old host port, issue the servicehost remove

[<node:slot:port>[<WWN_or_iSCSI_name> ... ]] command, where:

•

<node:slot:port> is the old port location.

•

<WWN> is the WWN path or paths to the host to be removed.

•

<iscsi_name> is the iSCSI path or paths to the host to be removed.

Disconnect the host from the system and then connect it to the new port.

The system discovers the host on the new port automatically by matching the WWNs or iSCSI

Names of the inactive host you created in

Step 1

to the WWNs or iSCSI Names of the host.

The HP 3PAR OS automatically changes the state of the host from inactive to active. The host has immediate access to all volumes exported to the host.

Removing Host Paths

Host paths can be removed from the system before or after VLUNs are exported to the hosts. The removehost command removes a system host path to an FC or iSCSI host. If one or more paths are specified, the command removes only the specified paths; otherwise the entire host definition is removed. If VLUNs have been exported to the host, issue the removehost -rvl <host_name> command. For information about exporting VLUNs, see

“Unexporting Virtual Volumes” (page 91) .

The removehost CLI command is described in detail in the HP 3PAR Command Line Interface

Reference and the HP 3PAR CLI Help.

To completely remove a host definition from your system, issue the removehost <host_name>

[<WWN>... | <iscsi_name> ...] command, where:

•

<host_name> is the host definition to be removed.

•

<WWN>...

is the WWN path or paths to the host to be removed.

•

<iscsi_name>...

is the iSCSI path or paths to the host to be removed.

NOTE: Physically disconnecting a host server from the system port does not delete the host from the system.

70 Managing Ports and Hosts

Managing Host Autonomic Groups

Hosts can be combined into autonomic groups. Autonomic groups are sets of objects that can be managed as one object. If you have a group of hosts in a cluster and all the hosts require the same administrative procedures, it is easier to group those hosts into a set and manage them together.

Individual hosts can be members of multiple host sets.

Hosts added to a set inherit the rights of that set. For example, if a virtual volume is exported to a group of hosts and a new host is added to the host set, the new host can see the virtual volume as soon as it is added to the host set. The opposite is also true. If a host is removed from a set, all the rights of that host set are revoked for the removed host.

A host in a host set cannot be removed from the system until it has been removed from the host set, or until the host set is removed from the system. Removing a host set does not remove the hosts in that set. Changing the name of a host in a set does not change the rights of the host or remove it from the host set.

Creating Host Sets

Any hosts added to the host set automatically see all VLUNs available to the host set, provided there are no conflicting LUN IDs. If the added host has an exported LUN ID in the LUN ID range of the host set, the host cannot see the LUN and must be assigned a new ID. For more information about VLUN templates, see

“Exporting Virtual Volumes” (page 90)

To create a host set, issue the createhostset<set_name><host_names> command, where:

•

<set_name> is the name of the host set being created.

•

<host_names> are the names of the hosts included in the host set.

For a complete list of options available for the createhostset command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Adding Hosts to Host Sets

To add a host to an existing host set, issue the createhostset -add <set_name>

<host_names> command, where:

•

<set_name> is the name of the host set that will include the added hosts.

•

<host_names> are the names of the hosts being added to the host set.

For a complete list of options available for the createhostset command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Modifying Host Sets

To change the name of a host set, issue the sethostset -name <new_name> <set_name> command, where:

•

<new_name> is the new name of the host set.

•

<set_name> is the name of the host set being modified.

For a complete list of options available for the sethostset command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Removing Host Sets

If a host is removed from a host set, the removed host loses all the rights of the host set and cannot access volumes exported to the host set.

Managing Host Autonomic Groups 71

To remove a host set from the system, or to remove hosts from a set, issue the removehostset

<set_name> <host_names> command, where:

•

<set_name> is the name of the host set being removed or modified.

•

<host_names> are the names of the hosts being removed from the <set_name> host set.

This specifier is optional and it is not required if you are removing the entire set.

For a complete list of options available for the removehostset command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Managing Host Personas

A host persona is a set of behaviors that allows hosts that are connected to FC or iSCSI ports on the system to deviate from the default host behavior. By assigning a persona to a host, multiple host types that require distinct customized responses can share a single system port. For example, hosts that run Windows, Linux, and AIX operating systems can all connect to the same system port.

This simplifies connecting hosts to the system and reduces management costs related to complex host connections.

A host persona defines the custom responses for certain iSCSI commands and does not affect any of the FC port settings. Host personas are tied to the host name and identified by the host persona number. You can set the host persona number when the host is created or modify it later. Use the

HP 3PAR CLI commands or the HP 3PAR Management Console to display, create, modify, and remove host personas. See the HP 3PAR Command Line Interface Administrator’s Manual or the

HP 3PAR Management Console Online Help for instructions on displaying, creating, modifying, and removing host personas.

Different host personas have different functions and support different host operating systems. The specific host persona is designated by the host persona number. Depending on the selected host persona number, the following additional capabilities are supported:

•

UARepLun—Sends a unit attention when the VLUNs are added to or removed from the LUN list.

•

ALUA—Enables the asymmetric logical unit access (ALUA) command and asymmetric state change unit attention when path counts change due to adding or removing ports in the host's definition.

•

VolSetAddr—Enables HPUX Volume Set Addressing (VSA).

•

SoftInq—Enables inquiry data formats for hosts such as Egenera and NetApp.

•

NACA—Enables the Normal Auto Contingent Allegiance (NACA) bit for AIX.

•

SESLun—Enables iSCSI Enclosure Services (SES) LUN ID 254 for Host Explorer agent support.

•

SubLun—Enables SCSI two-level LUN addressing.

NOTE: Each host connected to the system must use a host persona with the SESLun enabled, or the Host Explorer agent cannot communicate with the system.

Table 5 (page 72)

describes the specific functionality for each host persona number. For a list of supported host operating systems, go to the Single Point of Connectivity Knowledge (SPOCK) website http://www.hp.com/storage/spock .

Table 5 Host Personas

Persona Number

Persona Name

Generic

Generic-ALUA

Generic-Legacy

Host Operating System Additional Capabilities

Linux, Windows, and Solaris UARepLun, SESLun

Linux, Windows, and Solaris UARepLun, ALUA, SESLun

Linux, Windows, and Solaris None

72 Managing Ports and Hosts

Table 5 Host Personas (continued)

Persona Number

Persona Name

HPUX-Legacy

AIX-Legacy

Egenera

NetApp ONTAP

VMware

Host Operating System

HP-UX

AIX

Egenera, NetApp

Data ONTAP

Linux and Windows

Additional Capabilities

VolSetAddr

NACA

SoftInq

SubLun, ALUA

NOTE: Only the Generic, Generic-ALUA, and Generic-Legacy personas are supported for iSCSI connections.

The NetApp host operating system requires unique WWNs for hosts in an FC fabric.

A host device must use either iSCSI or FC connections. Mixed ports are not supported on a single device.

The Host Explorer Software Agent

The HP 3PAR Host Explorer Software agent is a program that runs on a host connected to a system.

The Host Explorer agent runs as a service on Windows and as a daemon on Linux and Solaris operating systems. No license is required to use the HP 3PAR Host Explorer agent.

The Host Explorer agent communicates with the system over an FC or iSCSI connection and enables the host to send detailed host configuration information to the system. The information gathered from the Host Explorer agent is visible for uncreated hosts, and assists with host creation and diagnosing host connectivity issues.

When a host is created on the system, unassigned WWNs or iSCSI names are presented to the system. Without the Host Explorer agents running on the attached hosts, the system is unable to determine which host the WWN or iSCSI names belongs to, and you must manually assign each

WWN or iSCSI name to a host. With Host Explorer agents running, the system automatically groups WWNs or iSCSI names for the host together, assisting with creating the host.

The Host Explorer agent collects the following information and sends it to the system:

•

Host operating system and version.

•

FC and iSCSI HBA details.

•

Multipath driver and current multipath configuration.

•

Cluster configuration information.

You can install the Host Explorer agent from the HP 3PAR Host Explorer CD. For instructions on installing and using the Host Explorer agent, see the HP 3PAR Host Explorer User’s Guide. For a list of supported host operating systems, go to the HP SPOCK website: http://www.hp.com/storage/spock

To display the information returned by the Host Explorer agent to the system, issue the showhost

-agent or showhost -agent -d command.

Hosts and Virtual Domains

NOTE: Virtual domains requires the use of the HP 3PAR Virtual Domain Software license. Contact your local HP representative for details.

If you are using virtual domains, you can create and modify domain-specific FC or iSCSI hosts. In many instances, you follow the same process for creating and modifying hosts as you would for hosts that do not use domains.

The Host Explorer Software Agent 73

Creating a Domain-Specific Host

In order to create a domain-specific host, you must have Super or Edit rights in the all domain.

For details about this restriction, see the HP 3PAR StoreServ Storage Concepts Guide and the createhost command in the HP 3PAR Command Line Interface Reference.

To create a domain-specific host, issue the createhost command as described in createhost

“Creating a Host with a Fiber Channel Path” (page 67)

and

“Creating a Host with an iSCSI

Path” (page 67)

with the -domain <domain_name>|set:<set_name> option to specify the domain or domain set in which you are creating the host.

Modifying a Domain-Specific Host

Perform modifications to domain-specific hosts using the createhost and sethost commands, as discussed in

“Modifying Hosts” (page 68)

Any existing domain-specific host can be modified as follows:

•

By changing the host’s name. See

“Changing a Host Name” (page 68)

for instructions. You must have Super or Edit rights in the all domain, or Edit rights in a specified domain, to perform this operation. See the HP 3PAR StoreServ Storage Concepts Guide for details about domain restrictions.

•

By adding or removing WWNs or iSCSI names. This operation is restricted to users with Super or Edit rights in the all domain. For details about domain restrictions, see the HP 3PAR

StoreServ Storage Concepts Guide. See the following sections for instructions:

◦

“Adding Fiber Channel Path WWNs” (page 68)

◦

“Adding iSCSI Path iSCSI Names” (page 68)

◦

“Removing Fibre Channel Path WWNs” (page 68)

◦

“Removing iSCSI Path iSCSI Names” (page 69)

•

By adding or removing iSCSI CHAP authentication information. This operation is restricted to users with Super or Edit rights in the all domain (see the HP 3PAR StoreServ Storage Concepts

Guide for details about this restriction). See the following for instructions:

◦

“Configuring iSCSI CHAP Authentication Information” (page 69)

◦

“Removing iSCSI CHAP Authentication Information” (page 69)

Changing a Host Domain

This operation is restricted to users with Super or Edit rights in the all domain. For details about domain restrictions, see the HP 3PAR StoreServ Storage Concepts Guide.

For information about changing a host’s domain association, see

“Managing Domain Objects”

(page 60)

Using Persistent Ports for Nondisruptive Online Software Upgrades

The HP 3PAR OS 3.1.2 online software upgrade process does not require shutting down host-facing ports for an extended period of time. HP 3PAR OS 3.1.2 supports using persistent ports, or virtual ports, during the online software upgrade process in order to provide a transparent mechanism for maintaining host I/O with no disruptions.

Persistent ports allow HP 3PAR storage systems' host-facing ports to assume the identity of partner ports that are automatically designated by the system. For FC and FCoE ports, this is achieved through the use of N_Port ID Virtualization (NPIV). For iSCSI ports, this is achieved through the use of IP failover. The port failover operation takes place quickly enough to ensure that all host paths

74 Managing Ports and Hosts

stay online and host multipath software is not affected. The online software upgrade completes without any dependency on host multipath software.

Persistent ports can also be used to ensure nondisruptive host I/O activity for planned and unplanned node down time, such as HBA firmware upgrades, adding or replacing HBAs, adding or replacing

DIMMs, node failures, and cable or switch failures.

NOTE: FC connections can support more than one partner port. iSCSI connections are limited to one partner port due to the limitations of IP failover.

The following configuration requirements and limitations apply when using persistent ports for port-level failover:

•

The host port must be connected and zoned through fabric topology to a HP 3PAR storage system physical port.

•

The automatically-designated partner port must be connected to the same fabric as its partner port on the same switch.

•

The partner port does not have to be zoned to the host port.

•

Under normal conditions, a host port has a single I/O path to the storage array available.

•

If a partner port is zoned to the same host port as the primary port, the host port has two I/O paths to the storage array available.

•

The FC fabric used in the configuration must support NPIV.

•

Host-facing adapters on HP 3PAR storage systems used in the configuration must support NPIV.

•

FC adapters on hosts used in this configuration do not require NPIV support.

•

Port failover is only supported on target mode point to point port configurations.

Persistent port failover is only supported on the following NPIV-compliant HBAs:

•

HP 3PAR 4-port 4G FC

•

Emulex 2-port 4G

•

Emulex 4-port 8G FC

•

QLogic CNA in FCoE mode

•

QLogic 1G iSCSI

•

QLogic CNA in 10G iSCSI mode

Use the showport and showportdev commands to monitor the status of port failover and failback operations.

The operating system assigns failover ports using a fixed mapping of N¹:S:P. N¹ uses the XOR operator; therefore N¹ = N XOR 1. For example, port 0:1:1 partners with port 1:1:1. This means that port 0:1:1 provides failover for 1:1:1 and port 1:1:1 provides failover for port 0:1:1.

The showport command output includes Partner and FailoverState columns that display the partner port <node>:<slot>:<port> information and failover state information. FailoverState values represent the failover state of the two ports listed in the N:S:P and Partner columns. The

FailoverState value can be one of the following:

• none—No failover in operation.

• failover_pending—In the process of failing over to partner.

• failed_over—Failed over to partner.

• active—The partner port is failed over to this port.

• active_down—The partner port is failed over to this port, but this port is down.

• failback_pending—In the process of failing back from partner.

Using Persistent Ports for Nondisruptive Online Software Upgrades 75

In the showport command output shown below, primary port 0:0:1 corresponds to partner persistent port 1:0:1 with a failover of state of none.

root@snodeb40:S170# showport

N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol Label

Partner FailoverState

0:0:1 target ready 2FF70002AC0000AA 20010002AC0000AA host FC -

1:0:1 none

0:0:2 initiator ready 2FF70002AC0000AA 20020002AC0000AA disk FC -

- -

0:0:3 target loss_sync 2FF70002AC0000AA 20030002AC0000AA free FC -

1:0:3 none

0:0:4 target ready 2FF70002AC0000AA 20040002AC0000AA host FC -

- -

0:3:1 target loss_sync 2FF70002AC0000AA 20310002AC0000AA free FC -

1:3:1 none

0:3:2 initiator ready 2FF70002AC0000AA 20320002AC0000AA disk FC -

- -

0:5:1 initiator ready 2FF70002AC0000AA 20510002AC0000AA disk FC -

- -

0:5:2 target ready 2FF70002AC0000AA 20520002AC0000AA host FC -

1:5:2 none

0:6:1 peer offline - 0002AC53069C rcip IP RCIP0

- -

1:0:1 target ready 2FF70002AC0000AA 21010002AC0000AA host FC -

0:0:1 none

1:0:2 initiator ready 2FF70002AC0000AA 21020002AC0000AA disk FC -

- -

1:0:3 target loss_sync 2FF70002AC0000AA 21030002AC0000AA free FC -

0:0:3 none

1:0:4 initiator ready 2FF70002AC0000AA 21040002AC0000AA host FC -

- -

1:3:1 target loss_sync 2FF70002AC0000AA 21310002AC0000AA free FC -

0:3:1 none

1:3:2 initiator loss_sync 2FF70002AC0000AA 21320002AC0000AA free FC -

- -

1:5:1 initiator ready 2FF70002AC0000AA 21510002AC0000AA disk FC -

- -

1:5:2 target ready 2FF70002AC0000AA 21520002AC0000AA host FC -

0:5:2 none

1:6:1 peer offline - 0002AC520041 rcip IP RCIP1

- -

In the following example, port 0:0:1 is in the process of failing over to port 1:0:1.

root@snodeb40:S170# showport 0:0:1 1:0:1

N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol Label Partner

FailoverState

0:0:1 target offline 2FF70002AC0000AA 20010002AC0000AA free FC - 1:0:1

failover_pending

1:0:1 target ready 2FF70002AC0000AA 21010002AC0000AA host FC - 0:0:1

none

In this example, the failover from port 0:0:1 to port 1:0:1 has completed.

root@snodeb40:S170# showport 0:0:1 1:0:1

N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol Label Partner

FailoverState

0:0:1 target offline 2FF70002AC0000AA 20010002AC0000AA free FC - 1:0:1

failed_over

76 Managing Ports and Hosts

1:0:1 target ready 2FF70002AC0000AA 21010002AC0000AA host FC - 0:0:1

active

Issue the showport command with the -ids option to shows the identities currently hosted by each port. For example, with no failovers in operation, each port hosts its own single ID.

root@snodeb40:S170# showport -ids 0:0:1 1:0:1 0:4:1 1:4:1

N:S:P -Node_WWN/IPAddr- -----------Port_WWN/iSCSI_Name-----------

0:0:1 2FF70002AC0000AA 20010002AC0000AA

0:4:1 10.100.31.170 iqn.2000-05.com.3pardata:20410002ac0000aa

1:0:1 2FF70002AC0000AA 21010002AC0000AA

1:4:1 10.101.31.170 iqn.2000-05.com.3pardata:21410002ac0000aa

With failovers in operation, the identities are assigned to the partner ports.

root@snodeb40:S170# showport -ids 0:0:1 1:0:1 0:4:1 1:4:1

N:S:P -Node_WWN/IPAddr- -----------Port_WWN/iSCSI_Name-----------

0:0:1

0:4:1

1:0:1 2FF70002AC0000AA 21010002AC0000AA

2FF70002AC0000AA 20010002AC0000AA

1:4:1 10.101.31.170 iqn.2000-05.com.3pardata:21410002ac0000aa

10.100.31.170 iqn.2000-05.com.3pardata:20410002ac0000aa

Use the showportdev command to show the devices that are connected to physical ports. For persistent ports, the vp_WWN column indicates which persistent port WWN each device is associated with. For example, in normal mode, there is only a single native WWN hosted by the physical port.

root@snodeb40:S170# showportdev all 1:5:1

PtId LpID Hadr ----Node_WWN---- ----Port_WWN---- ftrs svpm bbct flen

-----vp_WWN-----

0x10300 0x01 0x00 2FF70002AC0000AA 21510002AC0000AA 0x8800 0x0012 n/a 0x0800

21510002AC0000AA

0x10b00 0x06 n/a 200000E08B041B50 210000E08B041B50 0x0000 0x03a2 0x0000 n/a

21510002AC0000AA

When the identity of port 0:5:1 has failed over to 1:5:1, the vp_WWN column is populated with the device identities of port 0:5:1.

root@snodeb40:S170# showportdev all 1:5:1

PtId LpID Hadr ----Node_WWN---- ----Port_WWN---- ftrs svpm bbct flen

-----vp_WWN-----

0x10300 0x01 0x00 2FF70002AC0000AA 21510002AC0000AA 0x8800 0x0012 n/a 0x0800

21510002AC0000AA

0x10b00 0x06 n/a 200000E08B041B50 210000E08B041B50 0x0000 0x03a2 0x0000 n/a

21510002AC0000AA

0x10301 0x01 0x00 2FF70002AC0000AA 20510002AC0000AA 0x8800 0x0012 n/a 0x0800

20510002AC0000AA

0x10b00 0x06 n/a 200000E08B041B50 210000E08B041B50 0x0000 0x03a2 0x0000 n/a

20510002AC0000AA

NOTE: When issuing the statport and histport commands, the statistics for a physical port reflect the aggregate for all persistent ports on the physical port.

Using Persistent Ports for Nondisruptive Online Software Upgrades 77

6 Managing CPGs and Virtual Volumes

Overview

A CPG creates a virtual pool of LDs that allows up to 4,095 virtual volumes to share the CPG's resources and to allocate space on demand. Virtual volumes draw their resources from CPGs, and virtual volumes are exported as Logical Unit Numbers (LUNs) to hosts. Virtual volumes are the only data layer visible to hosts. You can create physical copies or virtual copy snapshots of virtual volumes for use if the original base volume becomes unavailable. Before creating virtual volumes, you must first create CPGs to allocate space to the virtual volumes.

The system allows you to create a maximum of 2,048 CPGs on one system. For the maximum number of virtual volumes that can be created with your specific system configuration, go to the

HP SPOCK website: http://www.hp.com/storage/spock

For detailed information about CPGs and virtual volumes, see the HP 3PAR StoreServ Storage

Concepts Guide.

For instructions on how to create copies of volumes, see

“Managing Virtual Volume Copies”

(page 95)

NOTE: Creating TPVVs requires the HP 3PAR Thin Provisioning Software license. Creating virtual copies or snapshots requires the HP 3PAR Virtual Copy Software license. Contact your HP representative for more information.

Common Provisioning Groups

By default, a CPG is configured to auto-grow new LDs when the amount of available LD space falls below a configured threshold. CPGs are initially empty. The initial buffer pool of LDs starts off at a fraction of the exported virtual capacity of mapped volumes and automatically grows over time, as required by application writes. For detailed information about CPG growth warnings and growth limits, see the HP 3PAR StoreServ Storage Concepts Guide.

NOTE: Virtual volumes in the same CPG can share the same LD. In the unlikely event that the LD is damaged by multiple simultaneous disk failures, all the volumes associated with that LD will be unavailable.

Virtual volume performance may suffer from too much interleaving within the LDs.

Growth Increment Considerations for Common Provisioning Groups

The default and minimum growth increments vary according to the number of controller nodes in the system.

Table 6 Default and Minimum Growth Increments

Number of nodes

Default

32 GB

64 GB

96 GB

128 GB

Minimum

8 GB

16 GB

24 GB

32 GB

78 Managing CPGs and Virtual Volumes

There are several courses of action you can take such as adding physical disks to the system, or limiting the future growth of volumes that draw from the CPG. Your response can vary, depending on several factors:

•

Total available space on your system.

•

Nature of the data running on the system.

•

Number of CPGs in the system.

•

Number of volumes associated with those CPGs.

•

Anticipated growth rate of the volumes associated with the CPGs.

CAUTION: Use caution in planning CPGs. The system does not prevent you from setting growth warnings or growth limits that exceed the amount of currently available storage on a system. When volumes associated with a CPG use all space available to that CPG, either any new writes to TPVVs associated with the CPG will fail, or snapshot volumes associated with the CPG may become invalid, or both. Invalid volumes do not handle write failures gracefully and may produce unexpected failures.

Do not allow volumes that draw from a CPG to exceed the CPG's growth limit. Exceeding the CPG growth limit can invalidate snapshot volumes.

NOTE: By default, the growth warning and growth limits are set to none, which effectively disables these safety features.

See the HP 3PAR Messages and Operator’s Guide for additional information about specific alerts.

Managing alerts is described in

“Managing Events and Alerts” (page 118)

System Guidelines for Creating Common Provisioning Groups

When you use the advanced parameters for LD creation, use the following guidelines to ensure maximum performance and optimal reliability in the volumes supported by those LDs:

•

Chunklets in the same RAID set should be from different drive magazines or drive cages.

•

Chunklets in the same row should be from different physical disks. In other words, a physical disk should not appear twice in the same row.

•

Chunklets should belong to a disk that is connected through the primary path to the LD’s owner node.

•

The growth increment is limited to 40 chunklets.

•

The system should use as many physical disks as possible.

•

The load on all physical disks should be balanced.

•

The system should use the largest possible row size.

Common Provisioning Group CLI Commands

Use the following CLI commands to manage CPGs:

• showcpg

—display CPGs in the system.

• createcpg

—create CPGs.

• setcpg

—modify existing CPGs

• compactcpg

—consolidate LD space in CPGs into as few LDs as possible.

• removecpg

—remove CPGs from the system or remove specific LDs from CPGs.

Common Provisioning Group CLI Commands 79

Creating a Common Provisioning Group

•

To create a CPG, issue the createcpg -aw <percent> -sdgs <size> -sdgl <size>

-sdgw <size> -t <RAID_type> <CPG_name> command, where:

◦

-aw <percent> is the percentage of used snapshot space and administration space that will generate a warning alert. If 0 (default) is specified, alert generation is disabled.

◦

-sdgs <size> is the amount of LD storage created during each autogrow operation.

For the minimum default growth sizes per number of nodes, see

Table 6 (page 78) .

◦

-sdgl is the growth limit which cannot be exceeded during autogrow operations. If 0

(default) is specified, no limit is enforced.

◦

-sdgw <size> is the space limit for LD space before a warning alert is generated. If 0

(default) is specified, no warning limit is enforced.

◦

-t <RAID_type> is the RAID type, specified as r0 (RAID 0), r1 (RAID 1), r5 (RAID

5), or r6 (RAID MP).

◦

<CPG_name> is the name of the CPG being created.

If no RAID type is specified with the -t option, the default is RAID 1 for Fast Class (FC or SAS) and SSD device types, and RAID 6 for NL device types.

HP strongly recommends using RAID 6 for NL device types. If you want to use RAID 5 for NL device types, you must first change the setsys AllowR5OnNLDrives value to yes (the default is no).

For a complete list of options available for the createcpg command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Modifying a Common Provisioning Group

The following modifications are commonly performed on CPGs using variations of the setcpg command:

•

Specify the percentage of administration space or snapshot space that is used before an alert is generated.

•

Specify the amount of LD space created with each auto-grow operation.

For a complete list of options available for the setcpg command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Setting Snapshot Space Usage Warnings

To set or modify the space usage warning for a CPG, issue the setcpg -sdgw <size>

<CPG_name> command, where:

•

-sdgw <size> is the space limit for LD space before a warning alert is generated. If 0

(default) is specified, no warning limit is enforced.

•

<CPG_name> is the name of the CPG being created.

Setting a Common Provisioning Group’s Autogrow Size

NOTE: Before modifying your CPG’s autogrow settings, see

“Growth Increment Considerations for Common Provisioning Groups” (page 78)

for guidelines.

80 Managing CPGs and Virtual Volumes

To set or modify a CPG’s autogrow size, issue the setcpg -sdgs <size> <CPG_name> command, where:

•

-sdgs <size> is the amount of LD storage created during each autogrow operation. For the minimum default growth sizes per number of nodes, see

Table 6 (page 78) .

•

<CPG_name> is the name of the CPG being created.

Consolidating Common Provisioning Group Space

Compacting a CPG allows you to reclaim space from a CPG that has become less efficient in space usage from creating, deleting, and relocating volumes. Compacting consolidates LD space in CPGs into as few LDs as possible.

To consolidate CPG space, issue the compactcpg <CPG_name> or compactcpg <pattern> command, where:

•

<CPG_name> is the name of the CPG you wish to compact.

•

<pattern> is the pattern name to which matching CPGs are compacted.

For a complete list of options available for the compactcpg command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Removing a Common Provisioning Group

You cannot remove a CPG that still has virtual volumes provisioned from it.

To remove a CPG and the LDs that make up that CPG, issue the removecpg <CPG_name> command, where <CPG_name> is the name of the CPG being removed.

For a complete list of options available for the removecpg command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Virtual Volume Types

There are three types of virtual volumes:

•

FPVVs

•

TPVVs

•

Administrative Volumes

Administrative volumes are created by the system and are for system usage only.

CAUTION: It is strongly recommended that you do not tamper with the admin volumes.

Virtual volumes have three separate data components:

•

User space is the area of the volume that corresponds to the LD regions in the CPG available to the host. The user space contains the user data and is exported as a LUN to the host.

•

Snapshot space, also known as copy space, is the area of the volume that corresponds to LD regions in the CPG containing copies of user data that changed since a snapshot of the volume was created. The snapshot space contains the copy data.

•

Administration space, also known as admin space, is the area of the volume that corresponds to LD regions in the CPG that track changes to the volume since a snapshot was created. The administration space contains pointers to copies of user data in the snapshot space.

Administration space is managed by the system, not with the tools you use to manage user and snapshot space.

You can increase the size of volumes, the amount of user space, and the amount of snapshot space for volumes as the requirements increase. If the user space and snapshot space use all available space, the HP 3PAR Virtual Copy Software feature’s copy-on-write operation will fail. To avoid running out of user space, use TPVVs to automatically draw more user space from a CPG. The HP

Virtual Volume Types 81

3PAR OS automatically reclaims unused snapshot space from TPVVs and fully provisioned virtual volumes and returns the space to the LDs.

For greater administrative flexibility, you can provision the virtual volume’s user space and snapshot space from the same or different CPGs. If the virtual volume’s user space and snapshot space are on different CPGs, the user space remains available to the host if the CPG containing the snapshot space becomes full. To save time by not repeating tasks, you can create many identical virtual volumes at one time. For planning information about virtual volumes and copies of volumes, see the HP 3PAR StoreServ Storage Concepts Guide.

Fully Provisioned Virtual Volumes

A fully provisioned virtual volume is a volume that uses LDs that belong to an LD pool known as a

CPG. Fully provisioned virtual volumes are the default system volume and do not require any additional licenses. Unlike TPVVs, fully provisioned virtual volumes have a set amount of user space allocated in the system for user data. They require the system to reserve the entire amount of space required by the fully provisioned virtual volume, whether or not the space is actually used. The fully provisioned virtual volume size is fixed, and the size limit is 16 TB. You can set snapshot space allocation limits and usage warnings to help manage the growth of snapshot space. For detailed information about fully provisioned virtual volumes, see the HP 3PAR StoreServ Storage Concepts

Guide.

NOTE: Some fully provisioned virtual volumes may be designated as a CPVV in the HP 3PAR

CLI.

Thinly Provisioned Virtual Volumes

With an HP 3PAR Thin Provisioning Software license, you can also create TPVVs. A TPVV uses LDs that belong to an LD pool known as a CPG. TPVVs associated with the same CPG draw user space from that pool as needed, allocating space on demand in small increments, beginning with 256

MB per controller node. As the volumes that draw space from the CPG require additional storage, the system automatically creates additional LDs and adds them to the pool until the CPG reaches the user-defined growth limit that restricts the CPG’s maximum size. The TPVV volume size limit is

16 TB. For detailed information about TPVV growth warnings and growth limits, see the HP 3PAR

StoreServ Storage Concepts Guide.

Virtual Volume CLI Commands

Use the following CLI commands to manage FPVVs and TPVVs :

• showvv

—display virtual volumes in the system.

• createvv

—create virtual volumes.

• setvv

—modify existing volumes.

• growvv

—increase the size of existing virtual volumes.

• freespace

—free snapshot space from a virtual volume.

• removevv

—remove virtual volumes from the system.

• showvvset

—show information about a virtual volume set.

• createvvset

—create a virtual volume set, or add virtual volumes to an existing set.

• setvvset

—modify a virtual volume set.

• removevvset

—remove a virtual volume set, or virtual volumes from an existing set.

• checkvv

—validate and repair virtual volumes.

82 Managing CPGs and Virtual Volumes

Creating Virtual Volumes

After you create CPGs, you can create FPVVs and TPVVs that draw space from the CPGs. For greater administrative flexibility, you can provision the virtual volume’s user space and snapshot space from the same or different CPGs. If the virtual volume’s user space and snapshot space are on a different CPGs, the user space remains available to the host if the CPG containing the snapshot space becomes full. You can create many identical virtual volumes at one time. Expiration dates can be set for virtual volumes to save space.

For information about planning for the growth of virtual volumes, see the HP 3PAR StoreServ

Storage Concepts Guide. For information about creating CPGs, see

“Common Provisioning

Groups” (page 78) .

NOTE: Creating virtual copies or snapshots requires the HP 3PAR Virtual Copy Software license.

Creating TPVVs requires the HP 3PAR Thin Provisioning Software license. Contact your HP sales representative for more information.

NOTE:

If your system is accessible by an OpenStack cloud, you may see volumes with prefixes indicating that the volumes were created through the OpenStack cloud. Volumes created through the OpenStack cloud use the OpenStack Volume (OSV) and OpenStack Snapshot (OSS) prefixes.

Creating Fully Provisioned Virtual Volumes

A fully provisioned virtual volume has a set amount of user space that is allocated for user data.

The virtual volume’s snapshot space is allocated on demand.

To create a group of fully provisioned virtual volumes, issue the createvv -cnt <number>

-snp_cpg <CPG_name> <user_CPG> <VV_name> <VV_size g|G|t|T> command, where:

•

<number> is the number of virtual volumes to create with the designated properties.

•

<CPG_name> is the name of the CPG from which the created volume will draw its snapshot space and administration space.

•

<user_CPG> is the name of the CPG from which the created virtual volume will draw its user space.

•

<VV_name> is the name of the virtual volume being created.

•

<VV_size g|G|t|T> is the size of the volume in MB, GB, or TB. If g|G|t|T is not specified,

VV_size is the number of MBs. For example, 50g specifies 50 GBs.

NOTE: If the -tpvv option is not specified, the created volume is a fully provisioned virtual volume.

For a complete list of options available for the createvv command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Creating Thinly Provisioned Virtual Volumes

A TPVV allocates user space and snapshot space on demand. If you do not specify a CPG to be used for snapshot space with the -snp_cpg option, the TPVV will have no snapshot space.

To create a TPVV, issue the createvv -tpvv -snp_cpg <CPG_name> -usr_aw <percent>

-usr_al <percent> <user_CPG> <VV_name> <VV_size g|G|t|T> command, where:

•

-tpvv indicates that you are creating a TPVV.

•

<CPG_name> is the name of the CPG from which the volume will draw its snapshot space and administration space.

Creating Virtual Volumes 83

•

-usr_aw <percent> is the allocation warning alert limit for the user space specified as a percentage. This generates an alert when the user space of the volume exceeds a specified percentage of the volume’s size.

•

-usr_al <percent> is the allocation limit of the user space specified as a percentage.

This prevents the user space from exceeding a specified percentage of the volume’s size.

•

<user_CPG> is the name of the CPG from which the created virtual volume will draw its user space.

•

<VV_name> is the name of the volume being created. The name can be up to 31 characters.

•

<VV_size g|G|t|T> is the size of the volume in MB, GB, or TB. If g|G|t|T is not specified,

VV_size is the number of MBs. For example, 50g specifies 50 GBs.

For a complete list of options available for the createvv command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Modifying Virtual Volumes

Existing virtual volumes can be modified to use a new name, draw space from a different CPG, set allocation warnings, or to use new policies.

To modify a volume to draw its snapshot space and administration space from a different CPG, issue the setvv -snp_cpg <CPG_name> -usr_cpg <user_cpg> <VV_name> command, where:

•

<CPG_name> is the name of the CPG from which the modified volume will draw its snapshot space and administration space.

•

<user_CPG> is the name of the CPG from which the modified virtual volume will draw its user space.

•

<VV_name> is the name of the virtual volume being modified.

For a complete list of options available for the setvv command, see the HP 3PAR Command Line

Interface Reference and the HP 3PAR CLI Help.

Growing Virtual Volumes

You can increase the size of, or grow, an existing virtual volume’s user space automatically when the volume reaches capacity.

To automatically increase the user space available to a virtual volume when the volume reaches capacity, issue the growvv <VV_name> <size g|G|t|T> command, where:

•

<VV_name> is the name of the virtual volume you are growing.

•

<size g|G|t|T> is the amount of space automatically added to the user space in MB, GB, or TB. If g|G|t|T is not specified, VV_size is the number of MBs.

For a complete list of options available for the growvv command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Converting Virtual Volumes Online

You can convert existing fully-provisioned virtual volumes to TPPVs, and you can convert TPVVs to fully-provisioned virtual volumes on the array, without disrupting normal storage system operations and without requiring changes to any host applications that access the virtual volumes. If a TPVV is using most of its allocated storage capacity, you can convert the volume to a fully-provisioned virtual volumes in order to increase its storage capacity and allow for continued growth of the volume. When a TPVV reaches approximately 80% of capacity, the incremental benefit of capacity savings versus accelerating performance is weighted towards performance. In addition, converting

TPVVs to fully-provisioned virtual volumes can free up thinly-provisioned capacity for other TPVVs.

84 Managing CPGs and Virtual Volumes

Similarly, if a fully-provisioned virtual volume’s storage space is largely unused, you can convert it to a TPVV in order to save storage space.

Converting remote copy virtual volumes and virtual volumes that contain snapshots is not supported.

You can, however, convert virtual volumes with snapshots and use the -keepvv option to create a new virtual volume with a new WWN that contains the original LDs and snapshots, in order to retain those snapshots. Snapshots cannot be exported in order for the -keepvv option to work.

If the snapshots are exported, an error is returned.

Converting volumes from thin to full requires the HP 3PAR Dynamic Optimization license.

Converting volumes from full to thin requires the HP 3PAR Dynamic Optimization Software license and HP 3PAR Thin Provisioning Software license.

Converting Fully Provisioned Virtual Volumes to Thinly Provisioned Virtual Volumes

To convert an FPVV to a TPVV, issue the tunevv usr_cpg <cpg> -tpvv <VV_name>, where:

• usr_cpg <cpg> is the name of the CPG from which the converted virtual volume will draw its user space.

•

-tpvv indicates that you are converting the existing FPVV to a TPVV.

•

<VV_name> is the name of the virtual volume being converted.

Converting Thinly Provisioned Virtual Volumes to Fully Provisioned Virtual Volumes

To convert a TPVV to an FPVV, issue the tunevv usr_cpg <cpg> -full <VV_name>, where:

• usr_cpg <cpg> is the name of the CPG from which the converted virtual volume will draw its user space.

•

-full indicates that you are converting the existing TPVV to an FPVV.

•

<VV_name> is the name of the virtual volume being converted.

For a complete list of options available for the tunevv command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Reducing Volume Size with HP 3PAR Thin Conversion Software

HP 3PAR Thin Conversion Software is an optional feature that converts a traditional volume to a

TPVV. Virtual volumes with large amounts of allocated but unused space are converted to TPVVs that are much smaller than the original volume. Volumes are converted by creating a physical copy of the volume. During the conversion process, allocated but unused space is discarded and the result is a TPVV that uses less space than the original volume. To convert volumes located on a system, you must have an F-Class, T-Class, HP 3PAR StoreServ 10000 Storage, or HP 3PAR

StoreServ 7000 Storage system to perform the copy operation.

The conversion process has four steps:

Assessment.

Data preparation.

Zeroing unused space.

Creating a physical copy.

NOTE: Converting fully provisioned volumes to TPVVs with the Thin Conversion feature requires an F-Class, T-Class, StoreServ 10000, or StoreServ 7000 Storage system, an HP 3PAR Thin

Provisioning Software license, and an HP 3PAR Thin Conversion Software license. Contact your

HP representative for more information.

Reducing Volume Size with HP 3PAR Thin Conversion Software 85

Manually Converting a Fully Provisioned Virtual Volume to a Thinly Provisioned Virtual

Volume

To convert an FPVV to a TPVV:

For assessment and preparation considerations,, see the HP 3PAR StoreServ Storage Concepts

Guide.

Prepare the volumes for conversion to the new TPVV by removing unnecessary data. Perform clean-up tasks on the source volume by:

•

Emptying trash cans.

•

Archiving unused files.

•

Shrinking databases.

•

Deleting temporary files.

Use a host application to write zeros to the allocated but unused volume space. F-Class,

T-Class, StoreServ 10000, and StoreServ 7000 Storage systems detect and discard the zeros during the volume copy operation.

Convert the base volume to a TPVV by creating a physical copy of the volume. Create a physical copy of the base volume with the createvvcopy command. For more information, see

“Creating an Offline Physical Copy” (page 98)

F-Class, T-Class, StoreServ 10000, and StoreServ 7000 Storage systems detect and discard the zeros during the volume copy operation. The createvvcopy command automatically enables the zero_detect policy on the destination TPVV. After the copy operation is completed, the zero_detect policy is automatically disabled.

Use the showvv-s command to view the size of the TPVV created in

Step 4

. The destination

TPVV should use significantly less total reserved space, and have a smaller volume size than the original base volume.

Optional. After verifying the data on the converted destination TPVV, you can use the removevv command to remove the base volume converted in

Step 4 .

Reducing Volume Size with HP 3PAR Thin Persistence Software

HP 3PAR Thin Persistence Software is an optional feature keeps system TPVVs and read/write snapshots of TPVVs small by detecting pages of zeros during data transfers, and not allocating space for the zeros in the destination TPVV. This feature works in real-time and analyzes the data before it is written to the destination TPVV. You must have an F-Class, T-Class, StoreServ 10000, or StoreServ 7000 Storage system to use Thin Persistence with TPVVs. For more information about the Thin Persistence feature, see the HP 3PAR StoreServ Storage Concepts Guide.

To enable the Thin Persistence feature on a TPVV or a read/write snapshot of a TPVV, use the setvv command to enable the zero_detect policy on the destination TPVV. For more information, see

“Modifying Virtual Volumes” (page 84)

NOTE: Thin persistence can have some performance implications during extremely busy system conditions. HP recommends the zero_detect policy only be enabled during Thin Persistence and Thin Conversion operations. The zero_detect policy should be disabled during normal operation.

Maintaining TPVV and read/write snapshot size with the Thin Persistence feature requires an

F-Class, T-Class, StoreServ 10000, or StoreServ 7000 Storage system, an HP 3PAR Thin Provisioning

Software license, an HP 3PAR Thin Conversion Software license, and an HP 3PAR Thin Persistence

Software license. Contact your HP representative for more information.

86 Managing CPGs and Virtual Volumes

Managing Virtual Volume Autonomic Groups

Virtual volumes can be combined into autonomic groups. Autonomic groups are sets of objects that can be managed as one object. If you have a group of volumes used by a database or another application and all the virtual volumes require the same administrative procedures, it is easier to group those volumes into a set and manage them together. Individual virtual volumes can be members of multiple virtual volume sets.

Virtual volumes added to a set inherit the rights of that set. For example, if a group of virtual volumes is exported to a host and a new virtual volume is added to the virtual volume set, the new virtual volume is visible to the host as soon as it is added to the virtual volume set. The opposite is also true. If a virtual volume is removed from a set, all the rights of that virtual volume set are revoked for the removed virtual volume.

A virtual volume in a virtual volume set cannot be removed from the system until it has been removed from the virtual volume set, or until the virtual volume set is removed from the system. Removing a virtual volume set does not remove the virtual volumes in that set. Changing the name of a virtual volume in a set neither changes the rights of the virtual volume nor removes it from the virtual volume set.

Creating Virtual Volume Sets

To create a virtual volume set, issue the createvvset <set_name> <VV_names> command, where:

•

<set_name> is the name of the virtual volume set being created.

•

<VV_names> are the names of the virtual volumes included in the virtual volume set.

For a complete list of options available for the createvvset command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Adding Virtual Volumes to Virtual Volume Sets

To add a virtual volume to an existing virtual volume set, issue the createvvset -add

<set_name> <VV_names> command, where:

•

<set_name> is the name of the virtual volume set that will include the added virtual volumes.

•

<VV_names> are the names of the virtual volumes being added to the virtual volume set.

For a complete list of options available for the createvvset command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Modifying Virtual Volume Sets

To change the name of a virtual volume set, issue the setvvset -name <new_name>

<set_name> command, where:

•

<new_name> represents the new name of the virtual volume set.

•

<set_name> represents the name of the virtual volume set being modified.

For a complete list of options available for the setvvset command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Removing Virtual Volume Sets

To remove a virtual volume set from the system, or to remove virtual volumes from a set, issue the removevvset <set_name> <VV_names> command, where:

•

<set_name> is the name of the virtual volume set being removed or modified.

•

<VV_names> are the names of the virtual volumes being removed from the <set_name> virtual volume set. This specifier is optional and it is not required if you are removing the entire set.

Managing Virtual Volume Autonomic Groups 87

For a complete list of options available for the removevvset command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Freeing Virtual Volume Snapshot Space

To free unused snapshot administration and snapshot data space from a virtual volume that is not in use by the system, issue the freespace <VV_name> or freespace <pattern> command, where:

•

<VV_name> represents the names of the virtual volumes from which snapshot space is to be made available.

•

<pattern> represents the name of the pattern from which snapshot space is to be made available from all volumes matching that pattern name.

NOTE: The freespace command cannot be used if the virtual volume has snapshots, the virtual volume is a TPVV, or the TPVV was created with HP 3PAR OS release 2.2.4 or earlier.

For a complete list of options available for the freespace command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help. For information about tuning your system for better performance, see

“Performance Tuning” (page 173) .

Setting Expiration Times for Virtual Volumes

You can set virtual volume expiration times with the -exp option of the following commands:

• createvv

• setvv

• createsv

• creategroupsv

Use the -exp option to set an expiration time for any volume or copy of a volume. The expired virtual volumes are not automatically removed, so you must use the removevv command or the

System Scheduler to remove the expired volumes. The expiration time can be set during the volume creation time, or can be applied to an existing volume.

To set the volume expiration time for any volume, issue the setvv -exp <time> d|D|h|H

<VV_name> command, where:

•

-exp <time> d|D|h|H specifies the amount of time from the current time in which the volume will expire. The value for <time> must be a positive integer in the range of 1 hour to 43,800 hours (1,825 days). The value for <time> can be specified in days with d|D or hours with h|H. For example, 14d specifies 14 days.

•

<VV_name> is the name of the volume that is set to expire.

Setting Retention Times for Virtual Volumes

HP 3PAR Virtual Lock Software is an optional feature that enforces the retention period of any volume or copy of a volume. You must purchase the Virtual Lock license to use the -retained option. Locking a volume prevents the volume from being deleted intentionally or unintentionally before the retention period elapses. You can use Virtual Lock to specify the retention period for any volume or copy of a volume.

Use the showvv -retained command to display all volumes with retention times, and the time at which the volume retention expires.

Rules for using volume retention times:

•

The retention time can be set during volume creation or applied to an existing volume.

•

The retention time can be increased, but it cannot be decreased.

88 Managing CPGs and Virtual Volumes

•

If both of the retention time and expiration time are specified, the retention time cannot be greater than the expiration time.

•

The retention time can be set in hours or days. The minimum retention time is 1 hour and the maximum retention time is 43800 hours (1,825 days or 5 years). The default is 336 hours

(14 days). The vvMaxRetentionTime system parameter determines the maximum retention.

This parameter can be set with the setsys command.

•

The maximum retention time for a volume in a domain can be set during domain creation with the createdomain command, or applied to an existing domain with the setdomain command.

•

If the volume belongs to a domain, then the volume retention time cannot exceed the domain's maximum retention time.

•

A volume with remaining retention time cannot be removed until the end of the retention period.

You can use the -retain option to set volume retention times while issuung the following commands:

• createvv

• setvv

• createsv

• creategroupsv

To create a virtual volume that cannot be deleted for a specified number of hours, issue the createvv -retain <time> d|D|h|H <CPG_name> -snp_cpg <CPG_name> <user_CPG>

<VV_name> <VV_size g|G|t|T> command, where:

•

-retain <time> d|D|h|H specifies that the volume cannot be removed from the system for the specified number of hours or days. The value for <time> must be a positive integer in the range of 1 hour to 43,800 hours (1,825 days). The value for <time> can be specified in days with d|D or hours with h|H. For example, 14d specifies 14 days.

•

<CPG_name> is the name of the CPG from which the volume will draw its snapshot space and administration space.

•

<user_CPG> is the name of the CPG from which the created virtual volume will draw its user space.

•

<VV_name> is the name of the volume being created. The name can be up to 31 characters.

•

<VV_size g|G|t|T> is the size of the volume in MB, GB, or TB. If g|G|t|T is not specified,

VV_size is the number of MBs. For example, 50g specifies 50 GBs.

Removing Virtual Volumes

To virtual volumes, issue the removevv <VV_name> or removevv <pattern> command, where:

•

<VV_name> represents the names of the virtual volumes to be removed.

•

<pattern> represents the name of the pattern according to which virtual volumes are to be removed.

For a complete list of options available for the removevv command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Removing Virtual Volumes 89

Validating and Repairing Virtual Volumes

To verify that virtual volumes are valid, and to repair virtual volumes corrupted by an uncontrolled system shutdown, issue the checkvv {-y|-n} <VV_name> command, where:

•

{-y|-n} specifies that if validity errors are found they are to be corrected (-y), or left unmodified (-n). If this option is not specified, errors are not corrected.

•

<VV_name> represents the name of the virtual volume to be validated and repaired.

For a complete list of options available for the checkvv command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Exporting Virtual Volumes

Virtual volumes are the only logical storage component visible to hosts. A virtual volume can be exported, or made accessible, to one or more hosts. The host sees the exported volume as a LUN connected to one or more ports. Once the virtual volume is exported to a host, the host can send requests to the LUN.

A volume-LUN, or VLUN, is a pairing between a virtual volume and a logical unit number (LUN), expressed as either a VLUN template or an active VLUN. The maximum number of supported

VLUNs per host is 16,000. The maximum number of supported VLUNs per system is 32,000. For more information about VLUNs, see the HP 3PAR StoreServ Storage Concepts Guide.

NOTE: When adding virtual volume sets, leave a gap between the virtual volume set export and any further exports to allow for expansion. This example uses the next free VLUN from 100 onwards, which this allows you to take advantage of the auto LUN functionality while retaining separation between virtual volume set ranges: createvlun <VV_name> 100+

<host>|set:<host_set>.

Creating VLUN Templates

A VLUN template creates an association between a virtual volume and a LUN-host, LUN-port, or

LUN-host-port combination by establishing the export rule, or the manner in which the volume is exported. A VLUN template enables the export of a virtual volume as a VLUN to a host or hosts.

Those volume exports, which are seen as LUNs by the host or hosts, are active VLUNs.

A VLUN template can be one of the following types:

•

Host sees—allows only a specific host to see a volume.

•

Host set—allows any host that is a member of the host set to see a volume.

•

Port presents—allows any host on a specific port to see the volume.

•

Matched set—allows only a specific host on a specific port to see the volume.

Creating a Host Sees or Host Set VLUN Template

To create a host sees or host set VLUN template, issue the createvlun

<VV_name>|set:<set_name> <LUN> <host>|set:<host_set> command, where:

•

<VV_name> is the name of the virtual volume being exported to the host.

•

<set_name> is the name of the virtual volume set being exported to the host.

•

<LUN> is the LUN where the virtual volume is to be exported, expressed as an integer ranging from 0 through 16383.

90 Managing CPGs and Virtual Volumes

•

<host> is the name of the host to which the virtual volume is exported. This option creates a host sees VLUN template.

•

<host_set> is the name of the host set to which the virtual volume is exported. This option creates a host set VLUN template.

For detailed information about the createvlun command, see the HP 3PAR Command Line

Interface Reference.

Creating a Port Presents VLUN Template

To create a port presents VLUN template, issue the createvlun <VV_name>|set:<set_name>

<LUN> <N:S:P> command, where:

•

<VV_name> is the name of the virtual volume being exported to the host.

•

<set_name> is the name of the virtual volume set being exported to the host.

•

<LUN> is the LUN where the virtual volume is to be exported, expressed as an integer ranging from 0 through 16383.

•

<N:S:P> is the location of the target port used to export the virtual volume.

For detailed information about the createvlun command, see the HP 3PAR Command Line

Interface Reference.

Creating a Matched Set VLUN Template

To create a matched set VLUN template, issue the createvlun <VV_name>|set:<set_name>

<LUN> <N:S:P> <host>|set:<host_set> command, where:

•

<VV_name> is the name of the virtual volume being exported to the host.

•

<set_name> is the name of the virtual volume set being exported to the host.

•

<LUN> is the LUN to which the virtual volume is to be exported, expressed as an integer ranging from 0 through 16383.

•

<N:S:P> is the location of the target port used to export the virtual volume.

•

<host> is the name of the host to which the virtual volume is exported.

•

<host_set> is the name of the host set to which the virtual volume is exported.

For detailed information about the createvlun command, see the HP 3PAR Command Line

Interface Reference.

Unexporting Virtual Volumes

In order to halt the export of a virtual volume, you must remove the VLUNs associated with that volume. You must remove a VLUN template in order to remove the active VLUNs associated with that template.

Removing all VLUNs for a host stops the host from accessing any volumes.

Removing a Host Sees or Host Set VLUN Template

To remove a host sees VLUN template and all active VLUNs associated with it, issue the removevlun <VV_name>|set:<set_name> <LUN> <host>|set:<host_set> command, where:

•

<VV_name> is the name of the virtual volume.

•

<set_name> is the name of the virtual volume set.

•

<LUN> is the LUN for the virtual volume, expressed as an integer ranging from 0 through

16383.

Unexporting Virtual Volumes 91

•

<host> is the name of the host. This option creates a host sees VLUN template.

•

<host_set> is the name of the host set.

For detailed information about the removevlun command, see the HP 3PAR Command Line

Interface Reference.

Removing a Port Presents VLUN Template

To remove a port presents VLUN template and all active VLUNs associated with it, issue the removevlun <VV_name>|set:<set_name> <LUN> <N:S:P> command, where:

•

<VV_name> is the name of the virtual volume to halt exporting to the host.

•

<set_name> is the name of the virtual volume to halt exporting to the host.

•

<LUN> is the LUN that was exported, expressed as an integer ranging from 0 through 16383.

•

<N:S:P> is the location of the target port used to export the virtual volume.

For detailed information about the removevlun command, see to the HP 3PAR Command Line

Interface Reference.

Removing a Matched Set VLUN Template

To remove a matched set VLUN template and all active VLUNs associated with it, issue the removevlun <VV_name>|set:<set_name> <LUN> <N:S:P> <host>|set:<host_set> command, where:

•

<VV_name> is the name of the virtual volume being exported to the host.

•

<set_name> is the name of the virtual volume set being exported to the host.

•

<LUN> is the LUN that the virtual volume is to be exported, expressed as an integer ranging from 0 through 16383.

•

<N:S:P> is the location of the target port used to export the virtual volume.

•

<host> is the name of the host to which the virtual volume is exported.

•

<host_set> is the name of the host set to which the virtual volume is exported.

For detailed information about the removevlun command, see the HP 3PAR Command Line

Interface Reference.

Virtual Domains, CPGs, and Virtual Volumes

You can use the CLI to create and manage virtual volumes belonging to domains just as you would manage virtual volumes that do not use virtual domains.

NOTE: Virtual domains require the HP 3PAR Virtual Domains Software license. Contact your HP sales representative for details.

Creating a Common Provisioning Group in a Domain

If you are using virtual domains, you can create domain-specific CPGs which are accessible by only those users with rights to that domain. You must have Super or Edit rights in the all domain in order to create a domain CPG. For information about CPGs and virtual domains, see the HP

3PAR StoreServ Storage Concepts Guide.

92 Managing CPGs and Virtual Volumes

To create a CPG within a domain, issue the createcpg -domain <domain_name> -aw

<CPG_name> command, where:

•

<domain_name> is the domain in which you are creating the CPG.

•

-aw <percent> is the percentage of used snapshot space and administration space which will generate a warning alert. If 0 (the default value) is specified, no alerts are generated.

•

-sdgs <size> is the amount of LD storage created during each autogrow operation. For the minimum default growth sizes per number of nodes, see

Table 6 (page 78) .

•

-sdgl <size> is the growth limit which cannot be exceeded during autogrow operations.

If 0 (the default value) is specified, no limit is enforced.

•

-sdgw <size> is the space limit for LD space before a warning alert is generated. If 0 (the default value) is specified, no warning limit it enforced.

•

-t <RAID_type> is the RAID type, specified as r0 (RAID 0), r1 (RAID 1), r5 (RAID 5), or r6

(RAID MP).

•

<CPG_name> is the name of the CPG being created.

All arguments are identical to those specified in

“Creating a Common Provisioning

Group” (page 80)

. For a complete list of options available for the createcpg command, see the

HP 3PAR Command Line Interface Reference and the HP 3PAR CLI Help.

Creating Virtual Volumes in a Virtual Domain

If you are using virtual domains, you can create domain-specific virtual volumes which are accessible only by those users with rights to that domain. You must have Super or Edit rights in the domain in which you are creating the virtual volume. Virtual volumes are created by allocating resources from CPGs within a domain. A CPG must exist in the domain in which you wish to create a virtual volume before you can create a domain-specific virtual volume.

For instructions on creating domain CPGs, see

“Moving a Common Provisioning Group to a

Domain” (page 94) . For more information about virtual domains, see the HP 3PAR StoreServ

Storage Concepts Guide.

To create a virtual volume within a domain, issue the createvv <usr_CPG> <VV_name>

<VV_size g|G|t|T> command, where:

•

<usr_CPG> is the name of the CPG from which the created virtual volume’s user space is drawn.

•

<VV_name> is the name of the virtual volume being created.

•

<VV_size g|G|t|T> is the size of the volume in MB, GB, or TB. If g|G|t|T is not specified,

VV_size is the number of MBs. For example, 50g specifies 50 GBs.

For a complete list of options available for the createvv command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Modifying Virtual Volumes in Domains

Domain virtual volumes can be modified in the same way that virtual volumes in systems without domains can be modified. However, some restrictions apply to domain virtual volume modification.

•

If you are Super or Edit user belonging to the all domain, all virtual volume modification options for the setvv command are available for use and you can modify any virtual volume in the system.

•

If you are an Edit user belonging to a specified domain, all options for the setvv command are available for use for virtual volumes that belong to the same specified domain.

Virtual Domains, CPGs, and Virtual Volumes 93

See the HP 3PAR StoreServ Storage Concepts Guide and the setvv command in the HP 3PAR

Command Line Interface Reference for additional information about this restriction.

To modify a virtual volume in a domain, see

“Modifying Virtual Volumes” (page 84) .

Growing Virtual Volumes in Domains

Existing domain virtual volumes can be enlarged (grown) by automatically adding capacity in increments that you specify. Volumes which were created by Super or Edit users in the all domain can only be grown by Super or Edit users in the all domain. Volumes created from CPGs by Edit users in a specified domain can be grown by those users.

For instructions on growing domain virtual volumes, see

“Growing Virtual Volumes” (page 84) .

Freeing Virtual Volume Snapshot Space in Domains

The snapshot space in virtual volumes belonging to domains can be made available in the same way that virtual volumes in systems without domains are made available.

For instructions on freeing virtual volume snapshot space, see

“Freeing Virtual Volume Snapshot

Space” (page 88) .

Exporting Virtual Volumes in Domains

Creating VLUN templates in domains is procedurally no different from creating VLUN templates in systems that do not use virtual domains. If you are using virtual domains, you can export virtual volumes in your domains. The right to perform inter-domain exports is determined by the user’s role.

•

Users with Super and Edit rights who belong to the all domain can export virtual volumes in any domain existing in the system.

•

Users with Edit rights who belong to a specified domain can only export virtual volumes to hosts belonging to that domain.

Creating VLUN Templates in the All Domain

You can create host sees, matched set, and port presents VLUN templates if you have Super or

Edit rights in the all domain. For instructions on creating each template type, see

“Creating a

Host Sees or Host Set VLUN Template” (page 90) ,

“Creating a Port Presents VLUN

Template” (page 91)

, and

“Creating a Matched Set VLUN Template” (page 91)

Creating VLUN Templates in a Specific Domain

Edit users belonging to a specified domain can export virtual volumes to hosts belonging to that domain. Only host sees and matched set VLUN templates may be created. For instructions on creating each template type, see

“Creating a Host Sees or Host Set VLUN Template” (page 90)

and

“Creating a Matched Set VLUN Template” (page 91) .

Moving a Common Provisioning Group to a Domain

For instructions on moving CPGs into or out of a domain, see

“Managing Domain Objects”

(page 60)

94 Managing CPGs and Virtual Volumes

7 Managing Virtual Volume Copies

There are two types of copies that can be created from virtual volumes: virtual copies and physical

copies.

•

A virtual copy is a snapshot of an original or base volume. A virtual copy only records the changes to the original virtual volume.

•

A physical copy is a complete duplicate of all the data from a base volume to a destination volume.

For more information about virtual copies, see the HP 3PAR StoreServ Storage Concepts Guide.

NOTE: Creating TPVVs requires the HP 3PAR Thin Provisioning Software license. Creating virtual copies or snapshots requires the HP 3PAR Virtual Copy Software license.

NOTE:

If your system is accessible in an OpenStack cloud, you may see volumes with prefixes indicating that the volumes were created through the OpenStack cloud. Volumes created through the OpenStack cloud use the OpenStack Volume (OSV) and OpenStack Snapshot (OSS) prefixes.

Virtual Copies

A virtual copy is a snapshot of another virtual volume. You can make virtual copies of base volumes, physical copies, or other virtual copies. Virtual copies are created using copy-on-write techniques available only with the HP 3PAR Virtual Copy Software license. Unlike a physical copy which duplicates the entire base volume, a virtual copy only records the changes to the original volume.

This allows an earlier state of the original volume to be recreated by starting with the current state and rolling back all of the changes that have been made since the virtual copy was created.

You can use the HP 3PAR CLI to perform the following virtual copy tasks:

•

Create

•

Promote

•

Modify

•

Remove

For additional information about virtual copies, see the HP 3PAR StoreServ Storage Concepts

Guide.

Creating a Virtual Copy

Virtual copies can be read-only or read/write. Read-only and read/write copies must alternate.

You can only make a read-only copy of a read/write volume and a read/write copy of a read-only volume. Expiration dates can be set for virtual copies to save space. The system allows you to make a maximum of 500 virtual copies of a base volume. Up to 256 virtual copies can be read/write copies.

The maximum number of virtual copies that can be created on a system is determined by the system configuration. For the maximum number of virtual copies that can be created with your specific system configuration, see the SPOCK website: http://www.hp.com/storage/spock

To create a virtual copy, or snapshot, of a virtual volume or a virtual volume set, issue the createsv

-ro <snapshot_name> <source_VV>|set:<set_name> command, where:

•

-ro specifies that the snapshot being created is read-only.

•

<snapshot_name> is the name of the snapshot being created.

Virtual Copies 95

•

<source_VV> is the name of the virtual volume being copied.

•

<set_name> is the name of the virtual volume set being copied.

For a complete list of options available for the createsv command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Promoting a Virtual Copy

If you have created multiple copies of a base volume, the data on a virtual copy can be rolled back to the base volume or to any of the virtual copy’s RW parents in the same tree by promoting a virtual copy. This copies the changes from the virtual copy back onto the base volume, overwriting the base volume with the copy. The virtual copy still remains on the system.

The virtual copy and the target of the promote must not be exported.

Only one promote operation is allowed at a time within a virtual volume family tree.

To promote a virtual copy back to a base volume or back to any of the virtual copy’s RW parents in the same virtual volume family tree, issue the promotesv <VC_name>|set:<set_name>

-pri high command, where:

•

<VC_name> is the name of the virtual copy being promoted.

•

<set_name> is the name of the virtual copy set being promoted.

•

-pri <high|med|low> specifies the priority of the copy operation before it is started. This option allows you to control the speed at which the task is performed. If this option is not specified, the operation is started with default priority of medium. High priority indicates that the operation will complete as fast as possible. Low priority indicates that the operation will run slower than the default priority task. You can use the -pri option to raise the priority of the task if your virtual volumes are unavailable and restoring access to the volume is the highest priority. However, raising the priority of the task may impact host I/O performance.

The priority of the task can also be changed, after it has begun, with the settask command.

For more information about changing the priority of a running task, see

“Setting the Priority of a Running Task” (page 128)

For a complete list of options available for the createsv command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

NOTE: The -halt option cancels a running virtual copy promotion operation. The RW parent volume is marked with the cpf status, which indicates that the promotion failed. The cpf status can be cleared using the promotevvcopy command or by issuing a new instance of the promotesv command. This option cannot be used in conjunction with any other option.

To halt volume export, you must delete all VLUNs associated with the volume as described in

“Unexporting Virtual Volumes” (page 91) . After you delete all VLUNs, you can use the volume as

the destination volume for a physical copy.

If you are using HP 3PAR Remote Copy Software, you can optionally promote the virtual copy if the base volume is in a Remote Copy group. See the HP 3PAR Command Line Interface Reference for detailed information about the promotesv command. For details about Remote Copy, see the

HP 3PAR Remote Copy Software User's Guide.

Modifying a Virtual Copy

Any existing virtual copy can be modified to have a new name, new allocation warnings and limits, and adhere to new policies. To modify an existing VV, issue the setvv command. For details on all of the setvv command arguments and their usage, see the HP 3PAR Command Line

Interface Reference.

96 Managing Virtual Volume Copies

Removing a Virtual Copy

To remove a virtual copy, issue the removevv <VV_name> command, where <VV_name> is the snapshot you are removing.

See the HP 3PAR Command Line Interface Reference for detailed information about the removevv command.

Creating a Group of Virtual Copies

The HP 3PAR CLI also allows for the creation of consistent group snapshots of a list of virtual volumes. A maximum group size of 100 virtual volumes can be specified when making a group of virtual copies.

To create group snapshots, issue the creategroupsv <copy_of_VV> command, where

<copy_of_VV> is the name of the virtual volume being copied.

NOTE: If you wish to copy multiple volumes, the <copy_of_VV> argument can be repeated multiple times on the command line for a single instance of the creategroupsv command.

For a complete list of options available for the creategroupsv command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Physical Copies

A physical copy is a full copy of a volume. The data in a physical copy is static; it is not updated with subsequent changes to the parent volume. The parent volume is the original volume that is copied to the destination volume. The parent volume can be a base volume, volume set, virtual copy, or physical copy. Creating physical copies does not require a separate license.

Physical copies can be online physical copies or offline physical copies. For online physical copies, the destination volume is automatically created and can be exported immediately. Offline physical copies require a destination volume that must have a user space size at least as large as the user space of the base volume being copied, and cannot be exported.

The maximum number of physical copies that can be created on a system is determined by the system configuration. For the maximum number of physical copies that can be created with your specific system configuration, see the SPOCK website: http://www.hp.com/storage/spock

A physical copy can only be made from a volume with enough free space to accommodate writes to that volume during the physical copy operation. In addition, the destination volume must meet the following conditions:

•

It must have snapshot space associated with it.

•

It must have at least as much user space as the volume being copied.

In addition to creating offline or online physical copies, you can also use the HP 3PAR CLI to resynchronize or promote offline physical copies. Online physical copies cannot be resynchronized or promoted.

For additional information about the rules governing physical copies, see the HP 3PAR StoreServ

Storage Concepts Guide.

NOTE: If the parent and destination volume are both TPVVs, only the space actually used is copied.

The createvvcopy command can be issued multiple times. However, the system allows only two physical copy tasks to run concurrently. Any additional physical copy tasks are queued, pending the completion of the active physical copy tasks.

Physical Copies 97

Creating an Offline Physical Copy

To create an offline physical copy of a virtual volume, issue the createvvcopy -p

<parent_volume | parent_volumeset> -s <destination_volume> | destination_volumeset> -pri high command, where:

•

-p <parent_volume | parent_volumeset> creates a snapshot of the parent volume or volume set, as identified by <parent_volume | parent_volumeset>, and copies the snapshot data to the destination volume.

•

<destination_volume> | destination_volumeset> is the name of the destination volume or volume set. The destination volume (or each member of the destination volume set) must be equal to or greater in size than the parent volume, must be a writable volume, and must not be exported as a VLUN.

•

-s saves the snapshot for quick resynchronization and retains the parent/copy relationship between the parent and destination volumes.

•

The priority of the task can also be changed after it is running by using the settask command.

For more information about changing the priority of a running task, see

“Setting the Priority of a Running Task” (page 128)

For a complete list of options available for the createvvcopy command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

NOTE: The -halt option cancels a running physical copy operation. The destination volume is marked with the cpf status, which indicates that the copy operation failed. The cpf status can be cleared by issuing a new instance of the createvvcopy command.

Creating an Online Physical Copy

To create an online physical copy of a virtual volume, issue the createvvcopy -p

<parent_volume> -online [-snp_cpg <snap_cpg>] [-tpvv] <destination cpg>

<destination volume> command, where:

•

-p <parent_volume> creates a snapshot of the parent volume, as identified by

<parent_volume>

, and copies the snapshot data to the destination volume.

•

-online specifies that the copy is to be performed online. The destination volume is automatically created and can be immediately exported.

•

[-snp_cpg <snap_cpg>]

(optional) specifies the snapshot CPG to associate with the destination volume.

•

[-tpvv]

(optional) indicates that the destination volume is a TPVV.

•

<destination cpg> specifies the destination CPG to use for the destination volume.

•

<destination volume> specifies the destination volume name for the copy operation

NOTE: The —online option cannot be used with the -r, -halt, -s, -b, or -pri options.

98 Managing Virtual Volume Copies

Creating a Group of Physical Copies

The HP 3PAR CLI also allows for the creation of consistent group physical copies of a list of virtual volumes. A maximum group size of 100 virtual volumes is recommended for making a group of physical copies.

To create group physical copies, issue the creategroupvvcopy -p -s

<parent_VV>:<destination_VV>-pri high command, where:

•

-p <parent_VV> creates a group of snapshots of the parent volume, as identified by

<parent_VV>

, and copies data from the snapshots to the destination volume.

•

-s saves the snapshot for quick resynchronization, and retains the parent/copy relationship between the parent and destination volumes.

•

-pri <high|med|low> specifies the priority of the copy operation before it is started. This option allows you to control the speed of the task. If this option is not specified, the operation is started with default priority of medium. High priority indicates that the operation will complete as fast as possible. Low priority indicates that the operation will run slower than the default priority task. You can use the -pri option to raise the priority of the task if your virtual volumes are unavailable and restoring access to the volume is the highest priority. However, raising the priority of the task may impact host I/O performance. This option cannot be used with

-halt option.

The priority of the task can also be changed after it is running with the settask command.

For more information about changing the priority of a running task, see

“Setting the Priority of a Running Task” (page 128)

•

<destination_VV> is the name of the destination volume. The destination volume must be equal to or greater in size than the parent volume, must be a writeable base volume, and must not be exported as a VLUN.

For a complete list of options available for the creategroupvvcopy command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

NOTE: If you wish to copy multiple volumes, the <parent_VV>:<destination_VV> argument can be repeated multiple times on the command line for a single instance of the creategroupvvcopy command.

The -halt option cancels a running group copy operation. The destination volume is marked with the cpf status, which indicates that the group copy operation failed. The cpf status can be cleared by issuing a new instance of the creategroupvvcopy command.

The creategroupvvcopy command can be issued multiple times. However, the system allows only two physical copy tasks to run concurrently. Any additional physical copy tasks are queued, pending the completion of the active physical copy tasks.

Resynchronizing a Physical Copy

At some point, you may want to resynchronize a physical copy with its original base volume because either virtual volume could have been modified since the copy operation was launched.

When you resynchronize a physical copy, the system copies changes from one volume in the physical copy pair to the other.

To resynchronize a physical copy, issue the createvvcopy -r <destination_VV> command, where -r <destination_VV> is the volume to be resynchronized with its parent volume. The snapshot is retained for quick resynchronization, and the parent-copy relationship is also retained.

Resynchronizing a Group of Physical Copies

Just as groups of physical copies can be created for a list of virtual volumes, those physical copies can also be resynchronized.

Physical Copies 99

To resynchronize a group of physical copies, issue the creategroupvvcopy -r

<destination_VV> command, where -r <destination_VV> is the volume to be resynchronized with its parent volume.

Snapshots of the parent volume must have been saved during their creation (using the -s option) in order to resynchronize the volumes.

Promoting a Physical Copy

Over time, physical copies and their base volumes can change as data is written to each. At some point the association between the two volumes may no longer be relevant. The association between a physical copy and a base volume is broken by promoting the physical copy back to the base volume.

To promote a physical copy back to a base volume, issue the promotevvcopy

<copy_name>|set:<set_name> command, where:

•

<copy_name> is the name of the physical copy being promoted.

•

<set_name> is the name of the physical copy set being promoted.

Creating an Online Copy

An online copy is a virtual volume copy operation that enables the physical copy or read-write virtual copy to be instantly available for export to hosts. The destination volume can be immediately exported and is automatically created by the command.

To create an online copy of a virtual volume, issue the createvvcopy -p <parent_volume>

-online [-snp_cpg <snap_cpg>] [-tpvv] <destination cpg> <destination volume> command, where:

•

-p <parent_volume> creates a snapshot of the parent volume, as identified by

<parent_volume>

, and copies the snapshot data to the destination volume.

•

-online specifies that the copy is to be performed online. The destination can be immediately exported and is automatically created.

•

[-snp_cpg <snap_cpg>] specifies the snapshot CPG to be associated with the destination volume.

•

[-tpvv] indicates that the destination volume should be a TPVV.

•

<destination cpg> specifies the destination CPG to use for the destination volume.

•

<destination_volume> is the name of the destination volume. The destination volume must be equal to or greater in size than the parent volume, must be a writeable volume, and must not be exported as a VLUN.

NOTE: Using the createvvcopy command with the -online option is incompatible with the

-r

, -halt, -s, -b, and -pri options.

For a complete list of options available for the createvvcopy command, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Snapshots and Domains

NOTE: Virtual domains require the Virtual Domains Software license. Contact your local HP representative for further details.

As with standard systems, virtual copies and physical copies can also be created in systems using virtual domains. Domain snapshot creation and modification does not differ from snapshot creation and modification in systems not using domains. Domain snapshot creation and modification is

100 Managing Virtual Volume Copies

limited to users with Super and Edit rights who belong to the all domain, and to users with Edit rights who belong to a specified domain. Snapshots inherit the domain of their parent volumes.

•

Virtual copies can be:

◦

Created. See

“Creating a Virtual Copy” (page 95)

for instructions.

◦

Promoted. See

“Promoting a Virtual Copy” (page 96)

for instructions.

◦

Modified. See

“Modifying a Virtual Copy” (page 96)

for instructions.

◦

Removed. See

“Removing a Virtual Copy” (page 97)

for instructions.

•

Physical copies can be:

◦

Created. See

“Creating an Offline Physical Copy” (page 98)

for instructions.

◦

Resynchronized. See

“Resynchronizing a Physical Copy” (page 99)

for instructions.

◦

Promoted. See

“Promoting a Physical Copy” (page 100)

for instructions.

Moving Snapshots

Snapshots can be moved in or out of a domain using the movetodomain command. This action is restricted to Super users in the all domain.

NOTE: If a snapshot is moved in or out of a domain, the snapshot’s base volume is also moved.

For further instructions see

“Moving Domain Objects to Another Domain” (page 60) .

Snapshots and Domains 101

8 Creating and Applying Templates

Overview

You can use the HP 3PAR CLI to create templates that enable you to apply a set of parameters that automatically create LDs, virtual volumes, or CPGs with the same or similar characteristics.

The following general rules apply to templates:

•

A property can either be included in a template or not included.

Properties are virtual volume, LD, or CPG attributes such as set size.

•

A property included in a template can have a defined value or have a value that is left

unspecified.

A property with a defined value has had a specific value assigned to it (for example, a set size of 2). A property with an unspecified value does not have a specific value assigned to it. When you apply a template that includes a property with one or more unspecified values, the system will either use the default value (when applicable) or calculate the optimized setting for you.

•

For all templates, you can either allow overrides of property values or not.

When you allow overrides of a property, users can modify that property's value when applying the template. When you do not allow overrides of a property, it is not possible to modify the defined value, system default, or system-calculated value for that property when applying the template.

Creating Templates

You can create three types of templates that can then be applied to create LDs, virtual volumes, and CPGs.

To create a template, issue the createtemplate <obj_type> <template_name> command, where:

•

<obj_type> is the object type the template is used to create. Specify VV, LD, or CPG for virtual volume, LD, or CPG, respectively.

•

<template_name> is the name of the template being created.

The VV, LD, and CPG templates have object-specific arguments that must be specified during creation.

Additionally, depending on the type of template you are creating, you may wish to specify other arguments to further refine the template’s parameters. For required and optional arguments specific to each template object type, see the HP 3PAR Command Line Interface Reference.

Applying Templates

Once you have created a template, you can apply that template to create LDs, virtual volumes, or

CPGs.

102 Creating and Applying Templates

Creating Virtual Volumes and Logical Disks Using a Template

To create a virtual volume and its underlying LDs using a template, issue the createvv -templ

<template_name> <VV_name> <size> command, where:

•

<template_name> is the name of the template being applied to the creation of the volume and LDs.

•

<VV_name> is the user-designated name of the virtual volume being created.

•

<size> is the size of the user volume.

In addition to using a template to create volumes and LDs, you can also apply any optional argument available for the createvv command. You can overwrite read/write parameters in the applied template with new options at the time of creation. However, read-only parameters in the template cannot be overwritten. For additional information, see the HP 3PAR Command Line Interface

Reference.

Creating a Common Provisioning Group Using a Template

To create a CPG using a template, issue the createcpg -templ <template_name>

<CPG_name> command, where:

•

<template_name> is the name of the template being applied to the creation of the CPG.

•

<CPG_name> is the user-designated name of the CPG being created.

In addition to applying a template to the creation of the CPG, you can also apply any optional argument available for the createcpg command. Read/write parameters in the applied template can be overwritten with new options at the time of creation. However, read-only parameters in the template cannot be overwritten. See the HP 3PAR Command Line Interface Reference for additional information.

Modifying Templates

You can modify a template at any time by adding, replacing, or removing template parameters, regardless of whether the template has been applied to create LDs, virtual volumes, or CPGs. When you edit a template, no changes are made to objects you have created with that template.

Viewing Template Parameters

Before modifying a template it may be helpful to view the template’s existing parameters:

•

To view a template’s current parameters, issue the showtemplate <template_name> command.

If name of the template you wish to modify is unknown, you can, alternately, filter and display templates by object type.

•

To view templates by object type, issue the showtemplate -t <type> command, where

<type> can be VV (virtual volume), LD (LD), or CPG (common provisioning group).

Adding and Replacing Template Parameters

To add parameters to an existing template or replace parameters in an existing template, issue the settemplate <option> <template_name> command, where:

•

<option> includes the parameter and, if applicable, the parameter’s value that is being added or replaced in the template. For a descriptive list of valid options that can be applied to your template, see the createtemplate command in the HP 3PAR Command Line Interface

Reference.

•

<template_name> is the name of the template being modified.

Modifying Templates 103

Removing Template Parameters

To remove parameters in an existing template, issue the settemplate -remove <option>

<template_name> command, where:

•

<option> is the parameter being removed from the template. The parameters are the options that you specified during the creation of the template. It is not necessary to specify the parameter’s value during removal.

•

<template_name> is the name of the template being modified.

Removing Templates

Removing a template deletes the template from the system, but does not delete objects created with that template.

To remove a template from the system, issue the removetemplate <template_name> command, where <template_name> is the name of the template being removed.

You can optionally remove templates matching a specific pattern by issuing the removetemplate

-pat <template_name|pattern> command. For details about this option, see the HP 3PAR

Command Line Interface Reference.

104 Creating and Applying Templates

9 Monitoring System and Physical Disk Capacity

Overview

The HP 3PAR CLI provides commands to show the amount of used space and available space in a system. These commands allow you to review space usage information at the system level and for each physical disk.

Use the following CLI commands to review space usage information:

• showpd

—displays configuration information about the physical disks in the system.

• showspare

—displays information about spare chunklets in the system.

• showsys

—displays an overview of the system’s capacity and connectivity.

System Capacity

The HP 3PAR CLI provides detailed views of the system’s total capacity, as well as the system’s total capacity by storage device type.

Determining Total System Capacity

To determine system capacity, issue the showsys -space command. The following is an example of the data returned by issuing this command: cli% showsys -space

--------System Capacity (MB)---------

Total Capacity : 557056

Allocated : 359424

Volumes : 179200

Base Volumes : 27648

User : 27648

Copy : 0

Admin : 0

CPGs (TPVVs & CPVVs) : 151552

Copy : 86016

Used : 1024

Unused : 84992

Admin : 65536

Used : 512

Unused : 65024

Unmapped : 0

System : 180224

Internal : 110592

Spare : 69632

Used : 0

Unused : 69632

Free : 197632

Initialized : 197632

Uninitialized : 0

Unavailable : 0

Failed : 0

As shown in the example above, system capacity is displayed in MBs. The first line displays the system’s total capacity, which is the sum of the allocated space (Allocated), free space (Free), and failed space (Failed).

The allocated space includes the following:

•

All base volumes and the volumes’ user, copy, and administration spaces.

•

Provisioned groups and volumes, and their used and unused copy and administration spaces.

Overview 105

•

Unmapped volumes.

•

System space, which includes administration volumes, log files, and physical disk system data, as well as used and unused spare space.

•

The free space includes the total free initialized and uninitialized spaces available for use.

Determining System Capacity by Physical Disk Type

You can display the total capacity for all physical disks of a specific type. There are three types of physical disks: FC, NL, and SSDs.

To display the total capacity for all physical disks of a specific type in a system, issue the showsys

-space -devtype FC|NL|SSD command.

NOTE: The output of the showsys -space -devtype FC|NL|SSD command is displayed in the same format as the showsys -space command output example in

“Determining Total

System Capacity” (page 105) .

Physical Disk Capacity

The HP 3PAR CLI allows you to view capacity for all physical disks in your system, capacity of physical disks by device type, and the capacity for a single physical disk in your system.

NOTE: The Device Speed number does not represent a rotational speed for SSDs without spinning media. It is meant as a rough estimation of the performance difference between the drive and the other drives in the system. For FC and NL drives, the number corresponds to both a performance measure and actual rotational speed. For an SSD, the number is to be treated as a relative performance benchmark that takes into account I/O per second, bandwidth, and the access time.

Determining Total Physical Disk Capacity

To view the total physical disk capacity of the system, issue the showpd -spacecommand. The following is an example of the data returned by issuing this command: cli% showpd -space

--------------------(MB)--------------------

Id CagePos Type -State- Size Volume Spare Free Unavail Failed

0 0:0:0 FC normal 139520 22272 8960 108288 0 0

1 0:0:1 FC normal 139520 13312 8704 117504 0 0

2 0:0:2 FC normal 139520 22272 8704 108544 0 0

3 0:0:3 FC normal 139520 13056 8704 117760 0 0

4 0:1:0 SSD normal 47360 1024 0 46336 0 0

5 0:1:1 SSD normal 47360 1024 0 46336 0 0

6 0:1:2 SSD normal 47360 1024 0 46336 0 0

7 0:1:3 SSD normal 47360 1024 0 46336 0 0

8 0:9:0 FC normal 139520 22272 8704 108544 0 0

9 0:9:1 FC normal 139520 13056 8704 117760 0 0

10 0:9:2 FC normal 139520 22272 8704 108544 0 0

11 0:9:3 FC normal 139520 12800 8704 118016 0 0

12 1:0:0 NL normal 7150008 22528 8704 108288 0 0

13 1:0:1 NL normal 7150008 13056 8704 117760 0 0

14 1:0:2 NL normal 7150008 2272 _8704 108544 0 0

15 1:0:3 NL _normal 7150008 3056 _8704 117760 0 0

16 1:9:0 FC normal 139520 22272 8704 108544 0 0

17 1:9:1 FC normal 139520 13056 8704 117760 0 0

18 1:9:2 FC degraded 139520 22016 8704 108800 0 0

19 1:9:3 FC normal 139520 13056 8704 117760 0 0

--------------------------------------------------------------------

20 total 2421760 286720 139520 1995520 0 0

106 Monitoring System and Physical Disk Capacity

As shown in the example above, physical disk capacity is displayed in MBs. The data columns are identified as follows:

•

—The physical disk ID.

•

CagePos

—The position of the physical disk within the drive cage. The format varies depending on the drive cage type.

•

Type

—The physical disk type. There are three types of physical disks: FC, NL), and SSD.

•

State

—The state of the physical disk. The following disk states can appear:

◦ normal

—The disk is normal.

◦ degraded

—The disk is not operating normally.

◦ new

—The disk is new and needs to be admitted with the admitpd command before it can be used.

◦ failed

—The disk has failed.

Use showpd -state to display detailed state information.

•

Size

—The disk’s capacity.

•

Volume

—The volume’s capacity.

•

Spare

—The disk’s space reserved for spare chunklets.

•

Free

—The disk’s free space.

•

Unavail

—Unavailable disk space.

•

Failed

—Space in failed chunklets.

Determining Physical Disk Capacity by Disk Type

You can display the capacity of all physical disks of a specific type. There are three types of physical disks: FC, NL, and SSD.

To display the total capacity for all physical disks of a specific type in a system, issue the showpd

-space -devtype FC|NL|SSD command.

NOTE: The output of the showpd -space -devtype FC|NL|SSD command is displayed in the same format as the showpd -space command output example in

“Determining Total Physical

Disk Capacity” (page 106) .

Determining the Capacity of a Specific Physical Disk

Physical disk capacity can be filtered by disk ID to display a specific disk’s capacity information.

NOTE: The output for the command listed below is displayed in the same format as the showpd

-space command output example in

“Determining Total Physical Disk Capacity” (page 106)

To display the capacity information for a single physical disk, issue the showpd -space <PD_ID> command, where <PD_ID> is the physical disk whose capacity information is shown.

Spare Chunklets

Some chunklets are identified as spares when the system is first set up at installation. Data from other chunklets is moved or reconstructed onto these spare chunklets in response to a chunklet or disk failure, or when a drive magazine needs to be serviced. This initial spare storage totals the amount of storage in a single drive magazine, using the largest size physical disks.

Spare Chunklets 107

How spare chunklets work:

•

When a connection is lost to a physical disk or a physical disk fails, all future writes to the disk are automatically written to a logging LD until the physical disk comes back online or until the time limit for logging is reached. Logging disk space is allocated when the system is set up.

•

If the time limit for logging is reached, or if the logging LD becomes full, relocation of chunklets on the physical disk to other chunklets, whether free chunklets or allocated spares, starts automatically. Free chunklets are chunklets that are not used by the system.

•

For automatic relocations, the system uses up a maximum of one disk worth of chunklets per system node.

NOTE: Local chunklets are chunklets on disks, which are used by the node that owns the LD for the chunklet being relocated.

•

If the system uses up its free or spare chunklets for relocation, an alert is generated.

•

Once the spare and free chunklets are used up, automatic relocation no longer occurs. In most cases, some data redundancy is lost. The system also generates an alert.

Viewing Spare Chunklets

Use the showspare command to display information about all spare chunklets. If a spare chunklet is in use, the showspare output includes the name and ID of the LD using it, as well as the chunklet’s position on the LD. If the spare chunklet is not in use, it is listed as available, and the columns relating to the LD show only dashes.

The following example displays information about two spare chunklets, 0 and 1, on physical disk

23:

%cli showspare

PdId Chnk LdName LdCh State Usage Media Sp Cl From To

23 0 ---- --- normal available valid Y Y --- ---

23 1 sales1.0 2 normal ld valid Y Y --- ---

The fields in this output provide the following information:

•

PdId

—The physical disk on which the chunklets reside.

•

Chnk

—The position on the physical disk of the spare chunklets.

•

LdName

—The name of the LD that is using the spare chunklet.

•

LdCh

—The position of the chunklet on the LD.

•

State

—The state of the chunklet as identified by the kernel. This value can be normal, none

(the chunklet has not been used by any LD), or failed.

•

Usage

—Shows whether the spare chunklet is in use by an LD. Values can be:

◦ available

—The chunklet is available for use as a spare.

◦ ld

—The chunklet is in use by an LD.

◦ relsrc

—Relocation source. The data has been moved to another chunklet.

◦ reltgt

—Relocation target. The data in the chunklet has been moved from another spare chunklet.

◦ abtrel

—Abort relocation. The system cancels the chunklet relocation operation.

◦ cmprel

—Completing relocation. The system is in the final phase of completing the chunklet relocation.

108 Monitoring System and Physical Disk Capacity

•

Media

—The current status of the physical disk media for the chunklet. The value is failed if the media has encountered errors and is unavailable, or valid if it is available for use.

•

—The spare status of the chunklet. Y indicates the chunklet is used for spare, N indicates that it is not.

•

—The cleaning status of the chunklet. Indicates whether the chunklet is in the process of being reinitialized for use, as happens when a physical disk is added to the system, or an LD is removed. The value can be Y (cleaned), N (not cleaned), or Cg (being cleaned now).

•

From

—The initial location of the chunklet prior to relocation. The format is PD:CH, where PD is the physical disk ID and CH is the chunklet ID.

•

—The destination location of the chunklet during relocation in the format PD:C H.

Logical Disks and Chunklet Initialization

After deleting logical disks, the underlying chunklets must be initialized before their space is available to build logical disks. The initialization process for chunklets generally takes about one minute per 1GB chunklet and 20 seconds per 256MB chunklet. To see chunklets that are currently in the process of being initialized, issue the showpd –c command. Chunklets that are uninitialized are listed in the Uninit column.

Recovering Failed RAID Sets

Failed RAID sets can prevent chunklet relocation, which in turn prevents servicemag operations from completing. Use the checkld command to recover data from a failed RAID set: checkld -y <LD_name> -rs <setnumber> -recover -fd:-fp

, where:

•

-y

—Indicates that any errors that are found should be fixed; this option is required when using the -recover option.

•

<LD_name>

—Specifies the name of the LD that contains the failed RAID set.

•

-rs <setnumber>

—Specifies the RAID set number within the LD to be checked, fixed, and recovered.

•

-recover -fd:-fp

—Specifies the chunklet to be recovered by physical disk and chunklet position.

Viewing Hardware Inventory

Use the showinventory command to display information about all the hardware components in the system. The command output is divided into sections such as the following:

•

Nodes

•

PCI Cards

•

CPUs

•

Internal Drives

•

Physical Memory

•

Power Supplies

•

Battery

•

Node Fans

•

Port Inventory

•

Cage Inventory

•

Disk Inventory

Recovering Failed RAID Sets 109

Along with specific component details, the showinventory command also displays the following information:

•

Part number

•

Serial number

•

Assembly part number

•

Assembly serial number

•

Spare part number

•

Model name

•

Revision

110 Monitoring System and Physical Disk Capacity

10 Data Encryption

Beginning with HP 3PAR OS 3.1.2 MU2, HP 3PAR encrypted storage systems provide data encryption by using self-encrypting drives (SEDs) with a local key manager (LKM).

Data encryption prevents data exposure that might result from the loss of physical control of disk drives when disk drives are:

•

Decommissioned at their end of life.

•

Returned for warranty or repair.

•

Lost or stolen.

The HP 3PAR StoreServ Data Encryption solution uses SED technology to encrypt all data on the physical drives and prevent unauthorized access to data-at-rest (DAR). When encryption is enabled, the SED will lock when power is removed, and it will not be unlocked until the matching key from the HP 3PAR StoreServ system is used to unlock it.

SEDs contain special firmware and an application-specific integrated circuit (ASIC) that provides encryption. Each SED has a number of bands that control access to different areas of the drive.

Each band has an internal encryption key that is not exposed outside of the drive itself. This encryption key is always used to encrypt and decrypt all data stored on that band. All data encryption is handled at the physical disk layer. System features, such as thin provisioning and dynamic optimization, work independently of encryption.

Each band has a single authentication key that controls access to data on the band. In the HP

3PAR StoreServ data-encryption implementation, the entire disk is in one band. Access to data is controlled by setting the authentication key, which locks and unlocks the drive.

The LKM, which is part of the HP 3PAR OS that runs on each node in a cluster, maintains the authentication key. You must back up and protect the keystore file; HP does not have access to the key.

All drives in the same array will have the same authentication key. The disks become locked whenever they lose power, which guarantees that any disk removed from an HP 3PAR Storage system will not be accessible except in its original array. When the drive is unlocked, all I/O to the drive behaves exactly as it would on a non-SED, and encryption and decryption happen at full interface speed, without data delays.

There is a minimal delay for booting (since each drive must be unlocked before the system becomes operational) and for data encryption management functions (since each disk must be updated whenever keys are changed on the system). Each of these operations takes up to 3 seconds per disk, but happens in several threads. On a system with 160 disks, for example, enabling encryption

111

takes about 30 seconds, and booting takes an additional 5 seconds. Rekeying under a light load takes about 15 seconds.

CAUTION:

Keep the encryption key file and password safe. If you lose the encryption key and the HP 3PAR

StoreServ system is still functioning, you can always perform another backup of the encryption key file. However, should you lose the encryption key file or the password, and should the HP 3PAR

StoreServ system then fail, the HP 3PAR StoreServ system will be unable to restore access to data.

Ensure that backup copies of the latest encryption key file are kept and that the password is known.

The importance of keeping the encryption key file and password safe cannot be overstated. HP does not have access to the encryption key or password.

Different arrays need separate backups, although the same password can be applied.

The SED DataStore provides an open interface for authentication key management. DataStore tracks the serial number of the array that owns each SED, which disallows SEDs from being used in other systems.

NOTE: The HP 3PAR data encryption solution will help mitigate breach notifications under the

Health Information Technology for Economic and Clinical Health (HITECH) Act, but is not compliant with the Federal Information Processing Standard (FIPS) 140-2.

Supported Configurations

HP 3PAR StoreServ Storage

The following HP 3PAR Storage systems support data encryption. They can be ordered with an

HP 3PAR Data Encryption license and SEDs that provide data encryption.

•

HP 3PAR StoreServ 10000 Storage

•

HP 3PAR StoreServ 7450 Storage

•

HP 3PAR StoreServ 7000 Storage

NOTE: A non-encrypting array cannot be converted to an encrypting array. HP does not support mixed configurations of encrypted and non-encrypted drives. The HP 3PAR StoreServ Storage system must be purchased new, with only SED drives installed.

HP 3PAR Operating System

•

HP 3PAR OS 3.1.2 MU2 or later

HP Peer Motion and HP Remote Copy are supported on data-encryption enabled systems. If the target system’s data-encryption state does not match the primary system’s data-encryption state when you are setting up HP Peer Motion or HP Remote Copy, you will get a warning that must be acknowledged in order to continue setting up. However, you will not be prevented from replicating encrypted data to a non-encrypting system.

Self-Encrypting Drives

SEDs are solid-state or hard disk drives.

Data Encryption Licensing

An HP 3PAR Data Encryption license is required to enable data encryption. This system-based encryption license key must be explicitly set by using the setlicense command.

112 Data Encryption

To view the license using the HP 3PAR CLI, issue the showlicense command: cli%showlicense

License key was generated on Thu May 23 16:29:37 2013

License features currently enabled:

...

Data Encryption

...

To view the license using the HP 3PAR MC, navigate to the Software tab.

Restrictions

These restrictions apply to the first release of data encryption (HP 3PAR OS 3.1.2 MU2):

•

Data encryption is available only with the purchase of a new HP 3PAR StoreServ system.

•

Data encryption cannot be enabled on an HP StoreServ storage system earlier than HP 3PAR

OS 3.1.2 MU2.

•

Data encryption is not supported on any HP 3PAR encrypted storage array with mixed configurations of SEDs and non-SEDs; the array must contain only SEDs.

•

A single authentication key is used to unlock all the drives in the array for reading and writing to media.

•

Authentication keys are managed using a local key manager (LKM) in the storage system.

•

The controlencryption commands (or GUI call) are recorded in the HP 3PAR OS eventlog, but the filename and password contents are not. For example:

Time : 2013-05-28 13:52:20 PDT

Severity : Informational

Type : CLI command executed

Message : {3parsvc super all {{0 8}} -1 127.0.0.1 9534} {controlencryption enable_start <password > <secret>} {}

Message : {3paradm super all {{0 8}} -1 16.94.229.83 9706} {controlencryption status_details} {}

Message : {3paradm super all {{0 8}} -1 16.94.229.83 30353} {controlencryption rekey_finish} {}

•

A user with Super authority is responsible for physical security of a backup copy of the authentication keys and for remembering the password.

•

Encryption should be enabled before writing data to the array. The system will function, and the same data can be accessed before and after encryption is enabled, but it will not be secure (no DAR) until encryption is enabled.

Using Self-encrypting Disks

Taking Ownership

Ownership means changing the authentication key and locking state of an SED from its default settings, so that the data on the drive is secure.

To enable the SED, issue the admitpd [option] [<WWN>...] command. Options are:

•

-nold

: Do not use the physical disk (as identifed by the WWN specifier) for LD allocation.

Specify the –nold option when adding a physical disk to replace a failed disk whose chunklets

Restrictions 113

were moved to spare space. Specifying -nold prevents the allocation of the newly added physical disk and allows chunklets to be moved back to the new disk. After chunklets have been moved back to the new disk, the administrator can allow LDs to be allocated again by issuing the setpd command.

•

-f

: Do not prompt for confirmation when attempting to admit disks from other systems.

•

WWN: Indicates the WWN of the physical disk to be admitted. If WWNs are specified, only the specified physical disks are admitted. Otherwise, all available physical disks are admitted.

For example: ci% admitpd

20 disks admitted

When disks are admitted to the system, the System Manager checks to see if they are SEDs. If they are SEDs, a cryptographic erasure is executed on the new drive, and ownership is taken (providing encryption was already enabled).

For more information about the admitpd command, see the HP 3PAR Command Line Interface

Reference.

Using the controlencryption command

Enabling Encryption

Because the key-file must be saved on the local disk (a customer PC or server), enabling encryption using the CLI must be performed from an HP 3PAR OS CLI Client running on a PC or server, or through the HP 3PAR MC, not from an SSH connection.

To enable encryption using the HP 3PAR CLI, issue the following command:

# controlencryption enable <backup filename>

To enable encryption using the HP 3PAR MC:

Under Command Actions, select Systems.

In the Encryption drop-down menu on the toolbar, select Enable Encryption....

To enable encryption using the Solaris or Linux CLI, issue the following command: cli% controlencryption enable backupfile

To enable encryption using the Windows CLI, issue the following command: cli% controlencryption enable C:\\backupfile

When encryption is initally enabled, the system verifies that:

•

The system is licensed for data encryption.

•

All drives in the system are SEDs.

•

There are no degraded or failed drives in the system.

If all of these conditions are met, the system generates an authentication key and returns the backed-up key file.

You will be prompted to twice for the password for the backup file. Backup is part of the encryption-enabling operation.

After the backup of the authentication key is acknowledged, the key is set on all the drives in the system.

For more information about the controlencryption command, see the HP 3PAR Command

Line Interface Reference.

114 Data Encryption

Backing up the Authentication Key File

To back up the authentication key file, issue the controlencryption backup command. For example: cli% controlencryption backup backup1

The keystore must be backed up to prevent total loss of data. You will be prompted to twice for the password for the backup file. The same password must be supplied on restore.

Restoring the Key File

Restoration of a key file is necessary only if there is a catastrophic problem and the key-files on all nodes are destroyed or corrupted. Restore the key-file from an external source to the controller nodes in the StoreServ system.

To restore the key file, issue the controlencryption restore command. For example: cli% controlencryption restore backup1

Rekeying the Authentication Key

To change the authentication key and back up the authentication key file, issue the controlencryption rekey command.

You can rekey the array at any time. You can also save and back up a new copy of the authentication key file at any time. In the event of a recovery action requiring restoration of the key file, the correct key file must be available; otherwise the data will be lost.

Showing Data Encryption Status

To see the status of data encryption, issue the following command: controlencryption status

Optionally, issue the command with the -d option to show disks that are failed or not SED-capable.

#$ controlencryption status

Licensed Enabled BackupSaved State SeqNum yes yes yes normal 2

#$ controlencryption status -d

Licensed Enabled BackupSaved State SeqNum Non-SEDs FailedDisks yes yes yes normal 2 0 0

Data encryption states (as seen under the State column in the foregoing example) are shown in

Table 7 (page 115) .

Table 7 Data Encryption States

System Encryption State initializing normal recovery_needed

Description

The data-encryption service is in the process of starting up.

Data encryption is in a normal state

Re-run the previous operation after addressing the reason why the previous operation failed (this is most likely to have been a failed drive).

in_progress

An encryption operation is in progress. A task is generated for the associated operations; the task can be reviewed in

Task Manager.

Using Self-encrypting Disks 115

Data encryption status information is shown in

Table 8 (page 116)

Table 8 Data Encryption Status

Status Information

Backup Saved

Licensed

Enabled

Non-SEDs

FailedDisks

Description

Yes if a backup has been saved.

No if a backup has not been saved and one is required.

The system is licensed with data encryption, but data encryption is not necessarily enabled.

Data encryption is enabled.

The number of drives that are not SEDs. If this number is non-zero, encryption operations cannot complete until these drives are removed from the system, as an encrypted system requires all drives to be self-encrypting.

Number of disks that are not usable. If this number is non-zero, encryption operations cannot be completed until these drives are removed from the system.

Replacing a Failed Disk Drive

The drive-replacement feature and the servicemag command function as they do in a system without data encryption. With data encryption, the old or failed drive will be locked when it is removed from the system. When the system detects a new drive, the drive will be cryptographically erased before it is admitted into the system.

For more information about the servicemag command, see the HP 3PAR Command Line Interface

Reference.

Upgrading an SED with New Firmware

Upgrades to the HP 3PAR OS function as they do for non-SEDs, except that SED drives have different firmware. Typically, the upgrade is performed automatically for users.

To upgrade a SED, issue the upgradepd [-f] [-skiptest] {-a | -w <WWN>... |

<PD_ID>...} command, where:

•

-f

: Upgrades the PD firmware without requiring confirmation.

•

-skiptest

: Skips the 10 second diagnostic test normally completed after each PD upgrade.

•

-a:

: Specifies that all PDs with valid IDs, and whose firmware is not current, are upgraded.

If this option is not specified, then either the -w <WWN> option or the PD_ID specifier must be issued on the command line.

•

-w <WWN>...

: Specifies that the firmware of either one or more PDs, identified by their

WWNs, is upgraded. If this option is not specified, then either the -a option or the PD_ID specifier must be issued on the command line.

•

<PD_ID>...

: specifies that the firmware of either one or more PDs identified by their IDs

(PD_ID) is upgraded. If this specifier is not used, then the -a option or the -w <WWN> option must be issued on the command line.

If the disk is locked, it will be unlocked. The digitally signed firmware will be downloaded.

116 Data Encryption

Dismissing an Existing SED

To remove the physical disk definitions from system use, issue the dismisspd <PD_ID>..., where <PD_ID>... specifies the PDs, identified by integers, to be removed. For example, to dismiss a PD with ID 1, issue the following command: cli% dismisspd 1

After the system manager (sysmgr) dismisses the drive, it is cryptographically erased (provided data encryption was enabled).

For more information about the dismisspd command, see the HP 3PAR Command Line Interface

Reference.

Data Encryption Commands

Table 9 Data Encryption Commands

Command controlencryption enable

Description

Enable data encryption on SEDs.

Back up the authentication key file.

controlencryption backup controlencryption restore controlencryption status

Back up the authentication key file.

Restore the key-file from an external source to the controller nodes in the

StoreServ system. This is needed only if there is a catastrophic problem and the key-files on all nodes are destroyed or corrupted.

Show the data encryption status. (See

“Showing Data Encryption Status” (page

115)

.) controlencryption rekey dismisspd servicemag

Change the authentication key.

Back up the authentication key file.

Dismiss and remove a drive from the system. This also performs a cryptographic erase operation on the drive.

Used to replace drives, especially in HP 3PAR StoreServ 10000 Storage systems.

Using Self-encrypting Disks 117

11 Managing Events and Alerts

Overview

The system tracks system events internally. Some of these events require action on the part of the system administrator, so they trigger alerts that are displayed for the administrator. Events are logs created by the system which allow you to view the day-to-day health of your system. Alerts are generated by the system when a system event requires immediate operator action or attention.

Checking the Status of a System

The checkhealth command checks the status of a system hardware and software components, and reports any issues. You can specify which components you want the checkhealth command to examine, or check all system components.

•

Use the checkhealth command to view a status summary of all system components.

•

Use the checkhealth -list command to view a list of all system components.

To check the health of specific hardware and software components, issue the checkhealth

<component> command, where <component> is the component, or list of components, you want to check.

For more information about troubleshooting your system with the checkhealth command, see the HP 3PAR F-Class, T-Class, and StoreServ 10000 Storage Troubleshooting Guide, HP 3PAR

StoreServ 7000 Storage Troubleshooting Guide, and HP 3PAR Messages and Operator’s Guide.

Monitoring and Managing Alerts

Alerts are system events that require your immediate attention. An alert may be triggered by a single event, a combination of events, or by repeated occurrences of the same event. The system administrator is responsible for responding to alerts. For information about system alerts, go to http://www.hp.com/support/hpgt/3par and select your server platform.

Viewing Alerts

To display system alerts, issue the showalert command.

You can additionally display alerts by type (fixed alerts, acknowledged alerts, and so on). For information about alert display options, see the HP 3PAR Command Line Interface Reference.

Setting an Alert State

To mark an alert as new, fixed, or acknowledged, issue the setalert new|fixed|ack

<alert_ID> command, where <alert_ID> is the alert whose status you wish to acknowledge.

Removing an Alert

To remove an alert, issue the removealert <alert_ID> command, where <alert_ID> is the alert you wish to remove.

Setting System Alerts

While most system alerts are generated automatically without any need for user configuration, there are several types of alerts that you can specifically configure:

•

Limits relating to CPGs can be set by the user when creating a CPG and can later trigger alerts. For information on setting the growth increment limits, see

“Common Provisioning

118 Managing Events and Alerts

Groups” (page 78) . For details about CPG creation precautions, see the HP 3PAR StoreServ

Storage Concepts Guide.

•

Limits for virtual volumes capable of allocating space on demand are also user-configurable and can trigger alerts. For information about on-demand virtual volume space allocation, see the HP 3PAR StoreServ Storage Concepts Guide.

•

The raw space alert is a global threshold that can be set for the storage system to alert administrators when available space on the system falls below a user-specified level. When the available space on the storage system falls below this user-specified threshold, an alert is generated.

There are also four default system thresholds which alert you when the available space on the system falls below 50%, 75%, 85%, and 95% of the total available space on the system. When the user-defined threshold is set, alerts for system thresholds below the user-defined threshold are suppressed. The following section describes how to set and change this raw space alert threshold.

Setting the Raw Space Threshold Alert

•

To set a raw space alert for a storage system with NL drives, issue the setsys

RawSpaceAlertNL <threshold> command.

•

To set a raw space alert for a storage system with FC drives, issue the setsys

RawSpaceAlertFC <threshold> command.

•

To set a raw space alert for a storage system with SSDs, ssue the setsys

RawSpaceAlertSSD <threshold> command.

For each command above, <threshold> is an integer from 100 to 100,000 that represents the total available space on the system in gigabytes. A value of 0 effectively disables the raw space alert safety feature. Any alerts for system thresholds below the user-defined thresholds are suppressed.

Monitoring and Managing the Event Log

The event log has information about all notable occurrences on the system. System events include all alerts the system has generated and alerts marked as acknowledged or fixed. These system events are generated and logged in the system event log.

By default, the HP 3PAR storage system reserves 3 MB for event log entries. However, the actual default size is 30 MB because the storage system maintains 11 versions of the event log: the current version, for writing new events to the log, and the past 10 versions for reading past events. When

11 versions have been written, the oldest event log is deleted. The 3 MB log size default value can be changed by administrators using the CLI setsys command EventLogSize parameter.

An event is logged if the event log size is changed. The current event log size can be obtained using the CLI showsys –param command.

cli% showsys -param

System parameters from configured settings

----Parameter----- ---Value----

RawSpaceAlertFC : 800

RawSpaceAlertNL : 0

RemoteSyslog : 1

RemoteSyslogHost : 192.168.6.15

SparingAlgorithm : Minimal

CopySpaceReclaim : 0

EventLogSize : 3M

VVRetentionTimeMax : 336 Hours

Monitoring and Managing the Event Log 119

Viewing the Event Log

To view the events log, issue the showeventlog command.

The eventlog display can be refined to include only events occurring before or after a specified time, within a specified time period, or that match a specified pattern. For complete information on the events log display options, see the HP 3PAR Command Line Interface Reference.

Removing the Event Log

To remove all event logs with severity Debug from the system, issue the removeeventlog command.

The removeeventlog command removes all event logs with severity Debug from the system.

Stopped Logical Disks and Missing Physical Disks

If physical disks in the system are unavailable when the system is powered on, the physical disk is in the Missing state. The system manager will not immediately start LDs that have chunklets on these missing disks. The result is some LDs remain in the Stopped state. Use the showpd and showld commands to display the state of physical and LDs.

If the LD is data-complete, but a few of the physical disks are missing, the LDs will be automatically started after waiting five minutes. If more than four physical disks are missing, the LDs will not be started automatically. You can start a data-complete LD using the InForm OS CLI startld command, and the system manager will begin reconstructing the missing mirrored data. The system automatically relocates the chunklets from the missing physical disks to free space or spare space.

For a complete list of options available for the showpd and showld commands, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Preserved Data

When the system is holding data in cache but is not able to write that data to the destination disk for any reason, it saves the data to the preserved data LD. This LD is automatically created at the time that the storage system is installed and initially configured.

The data written to the preserved data LDs is typically created due to a temporary loss of availability of disks, a situation that usually corrects itself once the disks become available again. When the destination LDs become available again, the system automatically plays back the preserved data by writing it from the preserved data LDs to the destination LDs.

If you notice that the preserved data LD has data saved for a long time, use the showpd command to see which physical disks are in an unavailable state. If any disks are in an unavailable state, it is necessary to take corrective action in order to make those disks available again. If data is persistently saved to the preserved data LD, contact your local service provider for technical support and services.

120 Managing Events and Alerts

12 Viewing Statistics and Histograms

Overview

The HP 3PAR CLI allows you to view aspects of system performance over time. You can view statistics for the performance of VLUNs, virtual volumes, ports, physical disks, data cache memory, and CPU usage, using variations of the stat command.

In addition, the HP 3PAR CLI provides service time and I/O size histograms for system resources such as chunklets, logical and physical disks, ports, VLUNs, and virtual volumes.

Viewing Statistics

This section provides instructions on using commonly used CLI commands to access performance statistics. The commands described here are a subset of the statistics commands available. For a complete list of statistics commands, see the HP 3PAR Command Line Interface Reference.

Performance statistics are available for the following:

• physical disks

• ports

•

VLUNs

• virtual volumes

• data cache memory

•

CPU usage

Viewing Statistics for Physical Disks

To view physical disk statistics, issue the statpd command.

Data output can be further refined to display only physical disk statistics from:

• a specific physical disk, specified by either its ID or WWN.

• specific nodes.

• specific PCI slots.

• specific ports.

Additional filters can be used to refine the data output. For complete details about statpd command options and for sample command data output, see the HP 3PAR Command Line Reference.

NOTE: The device speed number does not represent a rotational speed for SSDs without spinning media. It is meant as a rough estimation of the performance difference between the drive and the other drives in the system. For FC and NL drives, the number corresponds to both a performance measure and actual rotational speed. For an SSD, the number is to be treated as a relative performance benchmark that takes into account I/O per second, bandwidth, and the access time.

Viewing Port Statistics

To view port statistics, issue the statport command.

By default, only statistics for data transfers are displayed. You can optionally display statistics for control transfers, or both data and control transfers, by issuing the statport -ctl or statport

-both command, respectively.

Data output can be further refined to display only port statistics from:

• specific nodes.

• specific PCI slots.

Overview 121

• specific ports.

• host-connected (target) ports.

• disk-connected (initiator) ports.

•

FC ports (for Remote Copy).

•

Ethernet ports (for Remote Copy).

You can use additional filters to refine the data output. For complete details about statport command options and for sample command data output, see the HP 3PAR Command Line Reference.

Viewing VLUN Statistics

To view VLUN statistics, issue the statvlun command.

The data output can be further refined to display only VLUN statistics from:

•

Specific domains.

•

Specific hosts.

•

Specific virtual volumes.

•

Specific LUNs.

•

Ports from specific nodes, slots, or ports.

You can use additional filters to refine the data output. For complete details about statvlun command options and for sample command data output, see the HP 3PAR Command Line Reference.

Viewing Virtual Volume Statistics

NOTE: Virtual volumes may be accessed externally by hosts and internally by the system prefetcher.

When viewing virtual volume I/O statistics, the information provided by the HP 3PAR CLI includes access by the prefetcher. To see only external I/O statistics, view the VLUN statistics for a specific virtual volume/host combination.

To view virtual volume statistics, issue the statvv command.

To view remote copy virtual volume statistics, issue the statrcvv command.

By default, statistics for virtual volume read and write operations are displayed together. You can optionally display statistics for volume reads and writes separately by issuing the statvv -rw command.

You can use additional filters to refine the data output. For complete details about statvv and statrcvv command options and for sample command data output, see the HP 3PAR Command

Line Reference.

Viewing Statistics for Data Cache Memory

To view data cache memory statistics, issue the statcmp command.

By default, data cache memory statistics are displayed by node. You can optionally display data cache memory statistics by virtual volume by issue the statcmp -v command.

You can use additional filters to refine the data output. For complete details about statcmp command options and for sample command data output, see to the HP 3PAR Command Line

Reference.

Viewing Statistics for CPU Usage

To view statistics for CPU usage from all nodes, issue the statcpu command.

For complete details about statcpu command options and for sample command data output, see the HP 3PAR Command Line Reference.

122 Viewing Statistics and Histograms

Viewing Statistical Reports Using the On-node System Reporter

This section provides instructions on using HP 3PAR CLI commands to generate reports of historical capacity and performance information that has been collected by the on-node System Reporter.

The commands here are a subset of the statisics commands available. For a complete list of statistical reporting commands, see the HP 3PAR Command Line Interface Reference.

In nearly all cases, the reports can be refined by specifying the following:

•

A start time for the report

•

An end time for the report.

•

◦

Whether to view the data across a specified time period or at a specific time. For this report, you can also specify attributes by which to group like items together.

•

What granularity of samples to use in the report (high resolution – every 5 minutes, hourly, or daily).

Viewing Statistical Report for Region I/O Density

To view a statistical report for region I/O density, issue the srrgiodensity command. Data output can be further refined by the common fields listed in

“Viewing Statistical Reports Using the

On-node System Reporter” (page 123) , in addition to specifying a CPG name or an AO configuration

name. The report contains the distribution of IOP intensity for the LD region for a CPG or AO configuration.

For complete details about srrgiodensity command options and for sample command data output, see the HP 3PAR Command Line Reference.

Viewing Statistical Reports for Used Capacity (Space Reports)

To view statistical reports for capacity usage over time, issue the following commands. Most of these commands also allow the specification of the type of drive and RAID type for which to generate the report: sraomoves

Describes the space moved by Adapative Optimization over time between tiers in an Adapative Optimization configuration.

srcpgspace

Describes the space consumed in a CPG over time.

srldsapce

Describes the space consumed by LDs.

srpdspace srvvspace to describe the space consumed by physical disks.

to describe the space consumed by virtual volumes.

For complete details about command options and for sample command data output, see the HP

3PAR Command Line Reference.

Viewing Statistical Reports for Performance

Performance statistical reports are available for the following:

•

Cache memory

•

CPU

•

LDs

•

Links

•

Physical disks

•

Ports

•

Priority optimization

•

Virtual volume LUN exports

Viewing Statistics 123

Viewing Statistical Histogram Reports for Performance

Performance histogram statistical reports are available for the following. You can specify whether to display I/O time and/or I/O size, the number of histogram columns, and whether to separate read and write data or display the total I/O for:

•

LDs

•

Physical disks

•

Ports

•

Virtual volume LUN exports

Viewing Histograms

This section provides instructions on using common CLI commands to access histogram data on system resources. The commands described here are a subset of the histogram commands available.

Histogram data can be viewed for the following resources:

• chunklets

•

LDs

• physical disks

• ports

•

VLUNs

• virtual volumes

For a complete list of histogram commands, see the HP 3PAR Command Line Interface Reference.

Viewing Histograms for Chunklets

NOTE: The setstatch command must be issued to enable statistics collection on chunklets before chunklet histogram data can be viewed.

To view histogram data for chunklets, issue the histch command.

Several filters are provided to refine the data output to display only data from specific chunklets and LDs. Additional filters are provided to customize the way the histogram data is displayed. For complete details about histch command options and for sample command data output, see the

HP 3PAR Command Line Reference.

Viewing Histograms for Logical Disks

To view histogram data for LDs, issue the histld command.

The histld command provides filters to refine the data output to display only data from LDs mapped to specific virtual volumes. Additional filters are provided to customize the way the histogram data is displayed. For complete details about histld command options and for sample command data output, see the HP 3PAR Command Line Reference.

Viewing Histograms for Physical Disks

To view histogram data for physical disks, issue the histpd command.

Histogram data output can be further refined to display physical disk data from:

• a physical disk, specified by either its ID or WWN.

• specific nodes.

• specific PCI slots.

• specific ports.

124 Viewing Statistics and Histograms

You can use additional filters to customize the way the histogram data is displayed. For complete details about histpd command options and for sample command data output, see the HP 3PAR

Command Line Reference.

NOTE: The device speed number does not represent a rotational speed for SSDs without spinning media. It is meant as a rough estimation of the performance difference between the drive and the other drives in the system. For FC and NL drives, the number corresponds to both a performance measure and actual rotational speed. For an SSD, the number is a relative performance benchmark that takes into account I/O per second, bandwidth, and access time.

Viewing Histograms for Ports

To view histogram data for ports, issue the histport command.

By default, only histogram data for data transfers are displayed. You can optionally display histogram data for control transfers or both data and control transfers by issuing the histport

-ctl or histport -both command, respectively.

Histogram data output can be further refined to display only port data from:

• specific nodes.

• specific PCI slots.

• specific port slots.

• host-connected (target) ports.

• disk-connected (initiator) ports.

•

FC ports (for Remote Copy).

•

Ethernet ports (for Remote Copy).

You can use additional filters to refine the histogram data output and specify how that data is displayed. For complete details about histport command options and for sample command data output, see the HP 3PAR Command Line Reference.

Viewing Histograms for VLUNs

To view histogram data for VLUNs, issue the histvlun command.

Histogram data output can be further refined to display only VLUN data from:

•

Specific domains.

•

Sspecific hosts.

•

Specific virtual volumes.

•

Specific LUNs.

•

Ports from specific nodes, slots, or ports.

You can use additional filters to refine the histogram data output and specify how that data is displayed. For complete details about histvlun command options and for sample command data output, see the HP 3PAR Command Line Reference.

Viewing Histograms for Virtual Volumes

To view histogram data for virtual volumes, issue the histvv command.

To view histogram data for remote copy virtual volumes, issue the histrcvv command.

You can use additional filters to refine the histogram data output and specify how that data is displayed. For complete details about histvv and histrcvv command options and for sample command data output, see the HP 3PAR Command Line Reference.

Viewing Histograms 125

13 Managing Tasks

Overview

Some system operations with long running times can be managed as system tasks and initiated at scheduled times. The larger your system, the longer some CLI command operations take to complete.

With the task manager you can pause, cancel, or remove tasks running on the system. The System

Scheduler allows you to create, modify, and remove schedules for initiating tasks.

The group of CLI commands that can be managed with the task manager CLI commands is different from the group of CLI commands that can be scheduled with System Scheduler commands. For example, the tunevv command can be managed as a task but the tunevv command cannot be scheduled with System Scheduler commands.

•

See

Table 10 (page 126)

for a complete list of the task manager commands.

•

See

Table 11 (page 130)

for a complete list of the commands that can be managed with the task manager commands.

•

See

Table 12 (page 137)

for a complete list of the System Scheduler commands.

•

See

Table 13 (page 137)

for a complete list of the commands that can be scheduled with the

System Scheduler commands.

Task Manager

With the task manager CLI commands, you can display, cancel, or remove tasks running on the system.

Tasks are created in one of two ways:

• by a user or script issuing certain HP 3PAR CLI commands, such as the tunevv command.

• by the system initiating certain automated or scheduled processes, such as the periodic resynchronization of remote copy volumes groups.

Task IDs

Each task is identified by a task ID. When a task is started with the HP 3PAR CLI, the system displays the task ID as part of the command output. For example, when you issue the tunevv command with the HP 3PAR CLI, a task is started in order to track the progress of the tunevv operation.

The task ID is indicated in the output for the tunevv command. In the following example, Task454 is started as part of the tunevv operation.

cli% tunevv usr_cpg testcpg testvol

Task 454 started

Use the CLI showtask command to display the task IDs. For information about displaying task

IDs in the system, see

“Displaying Task Information” (page 127) .

Task Manager Commands

You can use the task manager commands to display, cancel, and remove tasks running on the system. See

Table 10 (page 126)

for a list of the HP 3PAR CLI task manager commands.

Table 10 Task Manager Commands

Command canceltask removetask

Description

Cancel one or more tasks.

Remove information about one or more tasks and their details.

126 Managing Tasks

Table 10 Task Manager Commands (continued)

Command settask showtask starttask waittask

Description

Set the priority of a running task.

Display information about tasks on the system.

Start a CLI command that runs as a background task.

Ask the CLI to wait for a task to complete before proceeding.

For a complete list of options available for the CLI task manager commands, see the HP 3PAR

Command Line Interface Reference and the HP 3PAR CLI Help.

Starting a Task

You can use the starttask command to start a CLI command that runs as a background_command task type. The background_command manages CLI commands with long running times in the background so that multiple tasks can run concurrently. The background_command task type can be managed with the task manager commands:

•

See

Table 10 (page 126)

for a complete list of the task manager commands.

•

See the background_command task type in

Table 11 (page 130)

for a list of the commands that can be run by the starttask command.

If the command running as a background_command requires user confirmation, you must force the command with the -f option.

To start a background_command task, issue the starttask <command_name> command, where:

•

<command_name> is the name of the CLI command to run as a background_command.

For a complete list of options available for the starttask command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Displaying Task Information

Once a task is started, you can use the task ID to obtain information about the task. To see a list of all tasks that have been active within the last 24 hours, you can use the showtask command without specifying a task ID. For example: cli% showtask

Id Type Name Status Phase Step -----Start_Time------ ---------FinishTime-------

1 vv_copy vv1a done 0/0 0/0 Wed Oct 06 18:44:05 EDT 2004 Wed Oct 06 18:44:57 EDT

2004

2 vv1b vv_copy active 2/3 0/8 Wed Oct 06 19:44:34 EDT 2004 --

All tasks are displayed by their task IDs, including active and completed tasks. The system stores information for up to 1,000 tasks. You can use the showtask-t <hours> command to show tasks older than 24 hours.

You can use the showtask -d command and the task ID to display status information about a specific ongoing or completed task. Task 454 is shown in the following example: cli% showtask -d 454

Id Type Name Status Phase Step ----------StartTime---------

--------FinishTime-------

454 tune_vv testvol done 0/0 0/0 Fri Apr 29 11:42:06 PDT 2005 Fri Apr 29 11:42:19

PDT 2005

Task Manager 127

Detailed status:

(...)

The columns in the example above are identified as follows:

•

—The task ID for the displayed task.

•

Type

—The task type. Task types are explained in

“Task Types” (page 130)

•

Name

—The name of the system object that is being operated on. When there are multiple objects, those objects are not identified individually but as a group (for example, multiple lds or multiple cpgs).

•

Status

—The task state. Task states are as follows:

◦ done

—The task has completed successfully.

◦ active

—The task is still in process.

◦ cancelled

—The task was cancelled by the user.

◦ failed

—The task failed to complete due to a reason other than user cancellation.

•

Phase

—For active tasks, indicates the number of completed phases and the total number of phases in the current step, using the format <#completed_phase>/<#total_phases>.

See individual task type descriptions for an indication of the number of phases for all tasks of that type.

•

Step

—For active tasks, indicates the number of completed steps and the total number of steps in the current task, using the format <#completed_step>/<#total_steps>. For most task types, the total steps is equal to the number of regions in the operation. See individual task type descriptions for step definitions.

•

Start Time

—Indicates the time at which the task was started.

•

Finish Time

—For done, cancelled, and failed tasks, indicates the time at which the task stopped due to completion, cancellation, or failure.

Use the showtask -t option to see older tasks. For a complete list of options available for the showtask command, see the HP 3PAR Command Line Interface Reference and the HP

3PAR CLI Help.

Setting the Priority of a Running Task

You can use the settask command to change the priority of a running physical copy operation or virtual copy promotion operation. Using the settask command with other task operations is not supported. You can also set the priority before running a task with the createvvcopy, creategroupvvcopy

, and promotesv commands and the -pri option. Task priorities can be set to high, medium, or low before or after the task is running. For more information about copies of volumes, see the

“Managing Virtual Volume Copies” (page 95) .

By default, physical copy operations and virtual copy promotion operations run as background tasks so they do not degrade host I/O performance. You can use the -pri option to raise the priority of the task if your virtual volumes are unavailable and restoring access to the volume is the highest priority. However, raising the priority of the task may impact host I/O performance.

The following example shows how to set the priority of task 497 to high.

cli% settask -pri high 497

Are you sure you want to set priority on task 497?

select q=quit y=yes n=no: y

high priority is set on task id: 497

128 Managing Tasks

For a complete list of options available for the settask command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Waiting for a Task

You can use the task ID and the waittask command to ask the system to wait for a task to complete before returning a command prompt. This prevents you from running too many tasks at once. If you use the waittask -v option, the command displays detailed task status and progress messages as the task executes.

For example: cli% waittask -v 454

Id Type Name Status Phase Step -----StartTime---- -----FinishTime--

454 tune_vv testvol Active 2/3 0/4 Fri Apr 29 11:42:06 PDT 2005

Detailed status:

{Fri Apr 29 11:42:06 PDT 2005} Created task.

{Fri Apr 29 11:42:06 PDT 2005} Tuning VV 'testvol'.

{Fri Apr 29 11:42:06 PDT 2005} Scheduled region move of 256MB from (testvol.usr.1:0MB)

to (testvol.usr.2:0MB).

{Fri Apr 29 11:42:06 PDT 2005} Scheduled region move of 256MB from (testvol.usr.0:0MB)

to (testvol.usr.3:0MB).

{Fri Apr 29 11:42:06 PDT 2005} Scheduled region move of 256MB from

(testvol.usr.1:256MB) to (testvol.usr.2:256MB).

{Fri Apr 29 11:42:06 PDT 2005} Scheduled region move of 256MB from

(testvol.usr.0:256MB) to (testvol.usr.3:256MB).

{Fri Apr 29 11:42:06 PDT 2005} Storing task data for later restarts.

{Fri Apr 29 11:42:06 PDT 2005} Started region move of 256MB from (testvol.usr.1:0MB)

to (testvol.usr.2:0MB).

{Fri Apr 29 11:42:06 PDT 2005} Started region move of 256MB from (testvol.usr.0:0MB)

to (testvol.usr.3:0MB).

{Fri Apr 29 11:42:06 PDT 2005} Started region move of 256MB from

(testvol.usr.1:256MB) to (testvol.usr.2:256MB).

{Fri Apr 29 11:42:06 PDT 2005} Started region move of 256MB from

(testvol.usr.0:256MB) to (testvol.usr.3:256MB).

{Fri Apr 29 11:42:19 PDT 2005} Completed region move of 256MB from

(testvol.usr.1:256MB) to (testvol.usr.2:256MB) in 13 seconds.

{Fri Apr 29 11:42:19 PDT 2005} Completed region move of 256MB from (testvol.usr.1:0MB)

to (testvol.usr.2:0MB) in 13 seconds.

{Fri Apr 29 11:42:19 PDT 2005} Completed region move of 256MB from (testvol.usr.0:0MB)

to (testvol.usr.3:0MB) in 13 seconds.

{Fri Apr 29 11:42:19 PDT 2005} Completed region move of 256MB from

(testvol.usr.0:256MB) to (testvol.usr.3:256MB) in 13 seconds.

{Fri Apr 29 11:42:19 PDT 2005} Waiting to switch regions to their new locations.

{Fri Apr 29 11:42:19 PDT 2005} Switching regions to their new locations.

{Fri Apr 29 11:42:19 PDT 2005} Reclaiming unused LD space.

{Fri Apr 29 11:42:19 PDT 2005} Deleted LD testvol.usr.1.

{Fri Apr 29 11:42:19 PDT 2005} Deleted LD testvol.usr.0.

{Fri Apr 29 11:42:19 PDT 2005} Cleaning up task data for later restarts.

{Fri Apr 29 11:42:19 PDT 2005} Completed region moves. Moved 4 regions for a total

of 1024 MB in 13 seconds.

NOTE: To cancel the waittask command, use CTRL-C. This stops the waittask command and returns a command prompt, but does not affect the task that is running in the background.

Task Manager 129

Removing a Task

The removetask command only works on completed, failed, and cancelled tasks. Information about a task remains on the system unless it is manually removed using the removetask command and the task ID. For example: cli% removetask 454

Remove the following tasks?

454 select q=quit y=yes n=no: y

The specified task ID and any information associated with it are removed from the system. However, task IDs are not recycled, so the next task started on the system will use the next whole integer that has not already been used (for example, 455). Task ID numbers roll over at 9999.

Canceling a Task

For all task types except remote_copy_sync, scheduled_task, snapspace_accounting, background_command

, and system_task, you can cancel an active task using the canceltask command and the task ID. For example: cli# canceltask <task_ID> select q=quit y=yes n=no: y

Information for the task will still be available with the showtask command, where the status of the task will now appear as Cancelled.

Task Types

See

Table 11 (page 130)

for a list of all task types and their associated operations. The table also includes information about the CLI commands associated with each operation. For a complete list of options available for the CLI commands listed in

Table 11 (page 130) , see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Table 11 Task Types by Operation and Command

Task Type Operation

(Feature or Product)

Commands Description background_command compact_cpg compact_lds promote_sv remote_copy_sync

The starttask CLI command.

Reclaim logical disk space.

Virtual copy promote (Virtual

Copy) (Remote Copy).

Remote copy volume synchronization (Remote

Copy).

creategroupsv createsv moverelocpd removevv updatevv upgradecage upgradepd

Tracks commands initiated by the starttask CLI command.

compactcpg compactld promotesv startrcopygroup

Compacts a CPG to reclaim space and reduce the number of LDs.

Compacts unused LD regions mapped to virtual volumes.

Copies the differences of a virtual copy back to its base volume.

Starts a remote copy volume group and synchronizes the primary and secondary groups.

130 Managing Tasks

Table 11 Task Types by Operation and Command (continued)

Task Type Operation

(Feature or Product)

Commands Description remote_copy_sync scheduled_task tune_sd tune_sys tune_vv tune_vv_restart tune_vv_rollback vv_copy

Remote copy volume synchronization (Remote

Copy).

System scheduler.

syncrcopy

Synchronizes remote copy volume groups.

snapspace_accounting startao system_task

Refresh the snapshot space usage information.

Starts an Adaptive

Optimization configuration.

Tasks initiated by the

3parsvc user.

updatesnapspace

-btsecs -etsecs

-maxrunh -compact

-dryrun

Tracks progress of the snapshot space usage accounting process.

Starts execution of an

Adaptive Optimization configuration using data region level performance data collected for the specified number of hours.

moverelocpd removevv

Tracks housekeeping tasks periodically run by the system.

Change the layout of a virtual volume (Dynamic

Optimization).

Tuning virtual volumes

(Dynamic Optimization).

tunevv snp _cpg

Perform space usage based analysis and tuning

(Dynamic Optimization).

tunesys tunevv

Restart tuning virtual volumes

(Dynamic Optimization).

Rollback tuning virtual volumes (Dynamic

Optimization).

Physical Copy.

checkhealth compactcpg compactld createsv creategroupsv createvvcopy creategroupvvcopy moverelocpd removevv syncrcopy tunepd tunevv updatesnapspace updatevv

Schedules when to initiate specified CLI commands.

tunevv restart tunevv rollback createvvcopy

Moves the LDs used for the volume’s snapshot space to the specified CPG.

Analyzes and automatically corrects space usage imbalances.

Changes the layout of the user space of an existing virtual volume.

Restarts a tunevv operation that was previously interrupted.

Rolls back a tunevv operation that was previously interrupted.

Copies a virtual volume.

Specific system tasks require the following licenses:

•

The promote_sv task type requires the HP 3PAR Virtual Copy Software license.

•

The remote_copy_sync task types require the HP 3PAR Remote Copy Software license.

•

The tune_vv task types require the HP 3PAR Dynamic Optimization Software license.

•

The tune_sd task type requires the HP 3PAR Dynamic Optimization Software license.

NOTE: Contact your HP representative for more information about HP licenses.

Task Types 131

background_command

The background_command task type tracks commands initiated by the starttask CLI command.

The background_command task type has only one phase and one step.

See the background_command task type in

Table 11 (page 130)

for a list of the commands that can be run by the starttask command.

See

“Starting a Task” (page 127)

for more information about the starttask command.

compact_cpg

The compact_cpg task type tracks the operations of the compactcpg command. For more information about compacting CPGs, see

“Compacting Common Provisioning Groups” (page 179)

The compact_cpg task type has only one phase, and the number of steps is equal to the number of LD regions to be moved.

compact_lds

The compact_lds task type tracks the operations of the compactld command. For more information about compacting LDs, see

“Compacting Logical Disks” (page 178) . The compact_lds

task type has only one phase, and the number of steps is equal to the number of LD regions to be moved.

promote_sv

The promote_sv task type is used to track virtual copy snapshot promote operations. Promoting a virtual copy snapshot copies the differences of the virtual copy back to its base volume. You can promote a virtual copy snapshot using the promotesv command; see the

“Promoting a Virtual

Copy” (page 96)

for details. Virtual copy snapshots may also be automatically promoted by systems using Remote Copy, for example when issuing the setrcopytargetreverse or setrcopygrouptarget commands on a primary storage system or a system with primary groups in order to reverse targets. Use of Remote Copy requires an HP 3PAR Remote Copy Software license.

For promote_sv tasks, there is only one phase. The number of steps in that phase is equal to the number of Gigabytes being copied.

NOTE: The promote_sv task type requires the HP 3PAR Virtual Copy Software license.

remote_copy_sync

The remote_copy_sync task type is used to track remote copy volume synchronizations on systems using Remote Copy. Remote Copy is an optional volume mirroring solution that can be used for disaster recovery and backup. The system creates a separate task for each primary volume undergoing synchronization.

You can initiate Remote Copy volume synchronizations manually by issuing CLI commands, or it can be performed automatically by the system. For instance, you can manually synchronize remote copy volume groups using the command. Restarting remote copy volume groups, by using the startrcopygroup command, can also initiate a remote copy synchronization on the system.

However, with periodic mode volume groups, the startrcopygroup command will initiate synchronization only the first time that it is issued for that volume group. In addition, periodic mode remote copy volume groups may be automatically resynchronized by systems using Remote Copy, but only if the resynchronization period has been set for the volume groups.

132 Managing Tasks

For remote_copy_sync tasks, there are three phases:

•

Phase 1 (startup): sync request has been received and synchronization is scheduled to start.

•

Phase 2: performing the resynchronization.

•

Phase 3: copying has completed and cleanup (such as deleting snapshots and setting state values) is taking place.

In the showtask output, the Step column indicates the completed and total volume size, in MBs, using the format <completed_size>/<total_size>.

For remote copy synchronizations, the finish time in the showrcopy output for the resynchronization task may not match the LastSync column in the showrcopy command output for the system holding the primary volumes. This is because the times are taken at different points in the process. The task time is set by the task subsystem when it is marked as completed, whereas the LastSync time is set when remote copy completes the sync. These two times should be similar, but may differ by up to a few seconds.

You cannot use the canceltask command to cancel a remote copy synchronization task.

For details about volume synchronizations and remote copy commands, see the HP 3PAR Remote

Copy Software User’s Guide.

NOTE: The remote_copy_sync task type requires the HP 3PAR Remote Copy Software license.

The tunevv CLI command requires the HP 3PAR Dynamic Optimization Software license.

scheduled_task

The scheduled_task task type is used to track system operations initiated by the System Scheduler commands. See

Table 12 (page 137)

for a complete list of the System Scheduler commands. See

Table 13 (page 137)

for a complete list of the CLI commands that can be initiated with the System

Scheduler commands. The scheduled_task task type has only one phase and one step.

snapspace_accounting

The snapspace_accounting task type tracks the progress of the snapshot space usage accounting process and runs the updatesnapspace command. The snapshot space usage displayed by showvv-s is not necessarily the current usage. You have to issue the showvv -hist command to display the last time updatesnapspace was run on the virtual volumes. The

TimeCalculated column shows the last time the usage was calculated. The updatesnapspace command causes the system to begin calculating current snapshot space usage. If one or more virtual volume names or patterns are specified, only the specified virtual volumes are updated. If no virtual volume names are specified, all virtual volumes are updated.

The updatesnapspacecommand immediately returns the task ID associated with the updated snapshot space usage accounting process. The canceltask command cannot be used to cancel the snapspace_accounting task type. To wait for completion, use the waittask command.

The snapspace_accounting task type has only one phase, and the number of steps is equal to the number of virtual volumes affected by the updatesnapspace command.

startao

When a startao command is scheduled, the user-defined schedule name appears in the list of schedules. The startao command syntax and operation are described in the HP 3PAR Command

Line Interface Reference, “Start Commands” section. For more information about Adaptive

Optimization concepts and usage, see

“Adaptive Optimization” (page 140)

Task Types 133

system_task

The system_task task type tracks the housekeeping tasks periodically run by the system. You can display any active housekeeping tasks with the showtask-all command. Only the 3parsvc user can run, change, or remove these tasks.

CLI housekeeping tasks and commands:

•

The move_back_chunklet runs the moverelocpd command.

•

The remove_expired_vvs runs the removevv command.

The system_task task type has only one phase and one step.

tune_vv

The tune_vv task type is used to track tunevv operations performed with the System Tuner tunevv command. Dynamic Optimization is an optional HP 3PAR OS feature that allows you to identify over-used physical disks and perform load balancing on them. The tunevv command enables you to perform load balancing and to dynamically change volume parameters.

You can suspend an active tune_vv task using the canceltask command and the task ID as follows: cli# canceltask <task_ID> select q=quit y=yes n=no: y

After cancelling the task, you can perform one of two additional operations:

•

You can restart the tunevv operation by using tunevv restart command. This starts a tunevv_restart task.

•

You can completely reverse the tunevv operation by using tunevv rollback command.

This starts a tune_vv_rollback task.

For tune_vv tasks, there are three phases:

•

Phase 1—Storing away region move information for future restarts and/or rollbacks.

•

Phase 2—Performing the actual region moves.

•

Phase 3—Deleting the information stored in Phase 1.

The number of steps in the phase is equal to the number of regions being moved.

For more information about the tunevv command, see

“Performance Tuning” (page 173) .

NOTE: The tune_vv task type and tunevv CLI command require the HP 3PAR Dynamic

Optimization Software license.

tune_vv_restart

The tune_vv_restart task type is used to track tunevv restart operations performed with the System Tuner tunevv restart command. The tunevv restart command enables you to resume a failed or cancelled tunevv operation.

CAUTION: Restart operations should not be performed on TPVVs.

The following examples shows how to start, cancel, and then restart a tunevv operation on virtual volume testvol: cli% tunevv -t r5 -ha mag testvol

Task 1 started.

134 Managing Tasks

cli% canceltask 1

Are you sure you want to cancel task 1?

select q=quit y=yes n=no: y cli% tunevv -restart testvol

Task 2 started.

Note that the tune_vv_restart task is a new task and receives a new task ID number.

After restarting the tunevv operation, you can use the showtask command to see the cancelled and restarted tasks: cli% showtask

Id Type Name Status Phase Step --------Start_Time------ ------Finish_Time-------

1 tune_vv testvol cancelled 2/3 8/8 Thu Oct 07 19:55:33 EDT 2004 Thu Oct 07 19:56:54

EDT 2004

2 tune_vv_restart testvol active 1/2 0/8 Thu Oct 07 19:57:23 EDT 2004 -

For tune_vv_restart tasks, there are two phases:

•

Phase 1—Performing the actual region moves.

•

Phase 2—Deleting the information stored in Phase 1 of the corresponding tune_vv task.

The number of steps in the phase is equal to the number of regions being moved.

For more information about the tunevv command, see

“Performance Tuning” (page 173) .

NOTE: The tune_vv task type and tunevv CLI command require the HP 3PAR Dynamic

Optimization Software license.

tunevv_rollback

The tune_vv_rollback task type is used to track tunevv rollback operations performed with the System Tuner tunevv rollback command. The tunevv rollback command enables you to reverse any changes that resulted from a previously interrupted tunevv operation.

The following examples shows how to start, cancel, and then rollback a tunevv operation on virtual volume testvol: cli% tunevv -t r5 -ha mag testvol

Task 3 started.

cli% canceltask 1

Are you sure you want to cancel task 3?

select q=quit y=yes n=no: y cli% tunevv -rollback testvol

Task 4 started.

Note that the tune_vv_rollback task is a new task and takes a new task ID number.

You cannot start a tune_vv_rollback task for a tunevv operation that completed successfully.

The following error message appears: cli% tunevv -rollback testvol2

Are you sure you want to rollback the tune process for VV 'testvol2' ?

select y=yes n=no: y

Task Types 135

Command failed error: No restart state for VV testvol2.

For tune_vv_rollback tasks, there are two phases:

CAUTION: Rollback operations should not be performed on TPVVs.

•

Phase 1—Performing the actual region moves.

•

Phase 2—Deleting the information stored in Phase 1 of the corresponding tune_vv task.

The number of steps in the phase is equal to the number of regions being moved.

For more information on System Tuner and the tunevv command see

“Performance

Tuning” (page 173) , and the HP 3PAR Command Line Interface Reference.

For more information about the tunevv command, see

“Performance Tuning” (page 173) .

NOTE: The tunevv CLI command requires the HP 3PAR Dynamic Optimization Software license.

tune_sys

The tune_sys task type is used to track operations performed with the tunesys command.

The tune_sys task has three phases:

•

Phase 1—Analyze the system, detect any virtual volume capacity imbalance between nodes, and rebalance the virtual volumes.

•

Phase 2—Detect any chunklet imbalance between physical disks associated with the same node and rebalance the chunklets.

•

Phase 3—Analyze the system and perform a consistency check on LDs to verify they match the characteristics of any CPG to which the LD belongs. Any LDs that do not match are modified to match the characteristics of the CPG.

The tune_sys task output displays information about the tuning process including:

•

Summary of tunesys command parameters.

•

Physical disk analysis.

•

Internode balance analysis.

•

Intranode balance analysis.

For more information about the tunesys command, see

“Performance Tuning” (page 173) .

NOTE: A dirty disk is a disk with chunklets that are determined to be out of balance during the analysis phase. A clean disk is a disk with balanced chunklets.

The tunesys command waits for chunklet cleaning between tuning operations in order to maximize the amount of space available for the next tuning operation.

tune_sd

The tune_sd task type is used to track the movement of the LDs used for the volume’s snapshot space to the specified CPG. Changing the layout of a virtual volume with the tunevv commands requires the HP 3PAR Dynamic Optimization Software license.

For tune_sd tasks, there are three phases:

•

Phase 1—Storing away region move information for future restarts, rollbacks, or both.

•

Phase 2—Performing the actual region moves.

•

Phase 3—Deleting the information stored in Phase 1.

136 Managing Tasks

The number of steps in the phase is equal to the number of regions being moved.

vv_copy

The vv_copy task type is used to track physical copy operations. This includes creating physical copies and resynchronizing a physical copy with its parent base volume. You can create physical copies using the createvvcopy command. See the HP 3PAR Command Line Interface Reference for details. You can also resynchronize a physical copy using the createvvcopy command with the -r resyncronization option. See

“Resynchronizing a Physical Copy” (page 99)

for details.

For vv_copy tasks, there is only one phase. The number of steps in that phase is equal to the number of gigabytes being copied.

System Scheduler

The System Scheduler allows you to create, modify, and remove schedules for initiating system operations with long running times. With the System Scheduler, commands you can schedule specific CLI commands to run at regularly scheduled intervals, or to run once at a specified time.

System Scheduler Commands

Table 12 (page 137)

summarizes the System Scheduler commands.

Table 12 System Scheduler Commands

Command showsched createsched setsched removesched

Description

Show the state of tasks currently scheduled on the system.

Create tasks to be initiated by the System Scheduler.

Modify tasks started by the System Scheduler.

Remove tasks initiated by the System Scheduler from the system.

Only the following command operations can be scheduled with the System Scheduler commands:

Table 13 Commands Initiated by the System Scheduler

Command checkhealth compactcpg compactld creategroupsv creategroupvvcopy createsv createvvcopy moverelocpd removevv setvv startao syncrcopy tunepd

Description

Displays the status of the system hardware and software components.

Consolidates LD space in a CPG into as few LDs as possible, allowing unused

LDs to be removed.

Consolidates space on the LDs.

Creates consistent group virtual copies or snapshots of a list of virtual volumes.

Creates consistent group physical copies of a list of virtual volumes.

Creates a virtual copy or snapshot of a virtual volume.

Creates a physical copy of a virtual volume.

Relocates chunklets to specified physical disks.

Removes virtual volumes from the system.

Modifies existing volumes.

Executes a specified Adaptive Optimization operation on the HP 3PAR OS.

Synchronizes Remote Copy volume groups.

Displays physical disks with high service times and optionally performs load balancing.

System Scheduler 137

Table 13 Commands Initiated by the System Scheduler (continued)

Command tunevv tunesys updatesnapspace updatevv

Description

Changes the layout of a virtual volume.

Analyzes and automatically corrects space usage imbalances.

Updates the snapshot space actually used by a virtual volume. This task cannot be cancelled.

Updates a snapshot virtual volume with a new snapshot.

The canceltask command cannot be used with the CLI commands initiated by the System

Scheduler commands. The task type scheduled_task can be canceled with the canceltask command by users with Super rights. The following task manager commands can be used on CLI command operations initiated by the System Scheduler with the task type scheduled_task:

• showtask

• waittask

• removetask

For more information about the task manager commands, see

“Task Manager Commands”

(page 126)

Displaying Scheduled Tasks

To display all scheduled user and system tasks, issue the showsched-all command.

To display specific scheduled tasks, issue the showsched <schedule_name>|<pattern> command, where:

•

<schedule_name> is the name of the schedule to display.

•

<pattern> displays all schedules that match the pattern.

For a complete list of options available for the showsched command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Scheduling Tasks

To create a scheduled task, issue the createsched <command> <task_schedule>

<schedule_name> command, where:

•

<command> is the name of the CLI command to be initiated. The CLI command must be one of the commands listed in

Table 13 (page 137) .

•

<task_schedule> is a crontab-style argument that specifies when the CLI command is initiated. You can use the minute, hour, day-of-month, month, and day-of-week format, or use one of the special entries to schedule when the CLI command is initiated.

•

<schedule_name> specifies the name of the schedule.

For a complete list of options available for the createsched command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

138 Managing Tasks

Modifying a Scheduled Task

To change the name of a scheduled task or change when the task is initiated, issue the setsched

-s <new_schedule> -name <new_name> <schedule_name> command, where:

•

<new_schedule> is a crontab-style argument that changes when the schedule is initiated.

You can use the minute, hour, day-of-month, month, and day-of-week format, or use one of the special entries to schedule when the CLI command is initiated.

•

<new_name> is new name to be applied to the existing schedule name.

•

<schedule_name> is the existing schedule name.

Suspending and Resuming Scheduled Tasks

To suspend or resume scheduled tasks, issue the setsched[-suspend|-resume]<schedule_name> command, where:

•

<suspend> suspends the schedule specified by the schedule name.

•

<resume> resumes the schedule specified by the schedule name.

•

<schedule_name> is the name of the schedule to suspend or resume.

NOTE: You can use the -suspend_all and -resume_all options in place of the -suspend and -resume options to suspend or resume all scheduled tasks in the system.

For a complete list of options available for the setsched command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

Removing Scheduled Tasks

To remove scheduled tasks, issue the removesched <schedule_name>|<pattern> command, where:

•

<schedule_name> is the name of the schedule to remove.

•

<pattern> is the name of the pattern according to which schedules are removed.

• removesched [options] <name|pat>

Where options are -pat and -f, without -pat the system does not match the pattern but looks for a specific name.

For a complete list of options available for the removesched command, see the HP 3PAR Command

Line Interface Reference and the HP 3PAR CLI Help.

System Scheduler 139

14 Adaptive Optimization

Adaptive Optimization (AO) uses System Reporter statistics gathered from LDs and physical disks to relocate customer data on physical volumes in an optimal way. AO relocation accomplishes two primary goals:

•

Increase performance of frequently accessed regions of data by moving those regions to higher-tier storage (for example, moving to SSDs from normal spinning media).

•

Improve cost-efficiency by moving lightly accessed regions of data to a lower performance and less expensive tier of storage (for example, moving from regular drives to NL drives).

Because storage tiers can be of different RAID types, capacity efficiency is maximized by using only RAID1 for the most frequently accessed storage and by using RAID5 or RAID6 for less frequently accessed storage. Other benefits include:

•

AO can migrate data from a fully occupied tier of storage to another tier that has more available capacity.

•

AO can also be regularly scheduled so that it can adjust the data layout as your data usage changes over time.

AO has been integrated into the HP 3PAR OS as part of changes in the 3.1.2 release. A simple user interface has been developed whereby AO can be started either as a scheduled task or as a manual command using the new startao command. For more information about tasks, see

“Managing Tasks” (page 126)

NOTE: Active use of AO requires an Adaptive Optimization license. Contact your local HP representative for information.

AO is built on top of the new version of System Reporter (SR), which also now runs as part of the

HP 3PAR OS.

SR must have been actively gathering data on VV regions for a period of time (a minimum of 3 hours, but preferable for a longer time including any time periods where the storage system has had peak load/usage).

The startao command is then used to perform an analysis of the data collected by SR to identify regions within virtual volumes that are either heavily used or lightly used, and then generates a series of secondary tasks to move these regions to faster or slower storage tiers.

Running AO on the HP 3PAR OS itself offers these advantages:

•

AO configurations can now be created, modified, and removed using the HP 3PAR CLI or the

HP 3PAR MC.

•

The database scheme has been restructured on node to be more efficient and reliable.

•

The actual movement of data can use data from a given time period in the past rather than only from the immediate past. This means data movement can occur at low-utilization time periods while using an analysis of statistics gathered during peak periods.

•

A time limit can be set for data movement so that scheduled data is moved only during low-utilization periods rather than during peak periods.

An AO configuration is specified as part of the startao command. When this is run as a scheduled task, details of the analysis and generated move commands can be viewed using showtask –d

, where <task id> is the ID of the startao command.

140 Adaptive Optimization

Adaptive Optimization Conversion

NOTE: This section applies only to HP 3PAR OS HP 3PAR OS 3.1.2. To modify an Adaptive

Optimization (AO) configuration in HP 3PAR OS 3.1.1 or earlier, see the “Changing an Adaptive

Optimization Configuration” section in the System Reporter Software User’s Guide..

Beginning with HP 3PAR OS 3.1.2, AO is implemented on the nodes together with an on-node version of System Reporter (SR). For HP 3PAR OS 3.1.1 or 2.3.1, AO is implemented by SR.

There is no direct conversion from external System Reporter-based AO configurations and HP 3PAR

OS 3.1.2 AO configurations created using the createaocfg command.

Table 14 (page 141)

lists the external SR AO configuration parameters and shows how they translate to createaocfg command options.

NOTE: The schedule and measurement intervals are not part of an AO configuration. Instead, the measurement interval is specified as options (-btsecs and -etsecs) for the startao command, and the schedule is implemented by using the createsched command to create a schedule to run the startao command.

Table 14 Adaptive Optimization Conversion Options

External SR

System name createaocfg option

AOCFG_name startao option

AOCFG_name

Comment

Specify a name for the AO configuration in the createaocfg command and use that name for the startao command as well.

The system name is not required because it is the system name itself on which the AO configuration is being created.

Tier 0 CPG

Name

-t0cpg

Tier 1 CPG

Name

Tier 2 CPG

Name

Tier 0

GiB

-t1cpg

-t0cpg

Tier 1

GiB

Tier 2

GiB

Schedule

Measure Hours -btsecs

-etsecs

Set a CPG warning or limit value for the tier

0 CPG instead.

Use setcpg —sdg <warn limit> for a warning limit, and setcpg

-sdgl <hard limit> for a physical limit).

Set a CPG warning or limit value for the tier

1 CPG instead.

Use setcpg —sdg <warn limit> for a warning limit, and setcpg

-sdgl <hard limit> for a physical limit).

Set a CPG warning or limit value for the tier

2 CPG instead.

Use setcpg —sdg <warn limit> for a warning limit, and setcpg

-sdgl <hard limit> for a physical limit).

The schedule is not part of the AO configuration. Instead, you can create a schedule using the createsched command to run startao on the AO configuration.

The measurement interval is not part of the

AO configuration; rather, it is an option of the startao command. To translate the measure hours directly into a startao

Adaptive Optimization Conversion 141

Table 14 Adaptive Optimization Conversion Options (continued)

External SR createaocfg option startao option Comment option, use the -btsecs option. For example, if the measure hours value is 2, use -btsecs

-2h

The startao is even more flexible, allowing you to specify not only the beginning of the measurement interval relative to the startao command start time, but also the end of the measurement interval relative to the startao command start time by using the -etsecs options.

For example, if the startao command is scheduled to run at 8 pm, you can specify

-btsecs -4h -etsecs -2h

, which specifies that the measurement interval starts

4 hours before the command start time (8 pm

-4 = 4 pm) and ends 2 hours before the command start time (8 pm -2 = 6 pm). So the measurement interval is 4 pm–6 pm for an 8 pm command start time.

Mode

-mode <mode> -mode Mode specifies one of the following modes:

•

Performance

•

Balanced

•

Cost

NOTE: The value of the mode is case-sensitive.

Active Because the AO configuration itself does not execute if the startao command is not run, there is no option to disable it. Instead, use setsched to suspend or resume the schedules that run startao on that AO configuration.

It is recommended that the CPG "warning limit" be used to limit AO use of a CPG. With a warning limit, VVs that use the CPG for growth can increase in size while limiting AO use of the CPG.

Creating an Adaptive Optimization Configuration

To create an AO configuration, use the createaocfg command.

NOTE: Two or more tier CPGs must be defined.

If domains are used, all CPGs must be either in the same domain or not in any domain.

A CPG can only belong to one AO configuration.

Active use of AO requires an Adaptive Optimization license. Contact your local HP representative for information.

142 Adaptive Optimization

Create an AO configuration using the createaocfg command.

Example: cli% createaocfg -t0cpg tier0_R1_SSD -t1cpg tier1_R6_FC -t2cpg tier2_R6_NL -mode

Performance AOCFG_name

where:

•

-t0cpg is the tier 0 CPG.

• tier0_R1_SSD is the tier 0 CPG name.

•

-t1cpg is the tier 1 CPG.

• tier1_R6_FC is the tier 1 CPG name.

•

-t2cpg is the tier 2 CPG.

• tier2_R6_NL is the tier 2 CPG name.

•

-mode <mode> specifies one of the following optimization biases for the AO configuration:

◦

Performance

: Move more regions towards higher performance tier.

◦

Balanced

: Balance between higher performance and lower cost.

◦

Cost

: Move more regions towards lower cost tier.

•

AOCFG_name is the name of the AO configuration (up to 31 characters in length).

NOTE: Tiers must be defined in “speed” order—tier 0 must be the fastest tier (SSD), tier 2 the slowest (NL). AO makes the assumption internally that tiers are defined in this speed order.

Set CPG warning limits to limit the size of tier 0 and tier 1, leaving tier 2 unlimited.

In the following example, the tier 0 limits are set to 64 g and the tier 1 limits to 256 g, respectively: cli% setcpg -sdgw 64g t0cpgname cli% cli% setcpg -sdgw 256g t1cpgname

Create a schedule to run startao on the AO configuration periodically.

In the following example, the AO configuration is set to run every day at 7:15 pm from Monday through Friday. The scheduled startao command considers 12 hours of statistics for its region moves. The 12 hours of statistics are from 7:15 am until 7:15 pm, as the -etsecs parameter was not specified.

cli% createsched "startao -btsecs -12h AOCFG_name" "15 19 * * 1-5" run_AOCFG_name

You can take advantage of several features that are not available in the external System Reporter by using the following options:

Table 15 Additional Options Not Available in an External System Reporter

Option

-maxrunh 6

Description

Instructs the startao to ensure that the command completes in 6 hours, limiting the number of region moves if necessary.

Creating an Adaptive Optimization Configuration 143

Table 15 Additional Options Not Available in an External System Reporter (continued)

Option Description

For the command in

Step 3 , this would ensure that the command would complete

by 11:15 pm.

CAUTION: When executed, this command attempts to complete the action within maxrunh hours, but success is not guaranteed.

-etsecs -4h

-compactcpg trimonly

Sets the end of the measurement interval 4 hours before the command starts. (With an external System Reporter, the measurement interval ends at the command start time.)

In the command in

Step 3 , this would mean that the end of the measurement interval

would be at 3:15 pm.

Instructs startao not to do a full compactcpg, but rather eliminate additional regionmoves within the CPG by doing only compactcpg -trimonly.

The following example shows how each of the options in

Table 15 (page 143)

is used. This command runs against data from 7:15 am until 3:15 pm Monday through Friday, completing by 1:15 am: cli% createsched "startao -btsecs -12h -etsecs -4h -compact trimonly -maxrunh 6

AOCFG_name" "15 19 * * 1-5" run_AOCFG_name

Displaying an Adaptive Optimization Setting

To display AO configurations in the system, use the showaocfg command: cli% showaocfg [-domain <domain_name_or_pattern>] [<AOCFG_name>...|<pattern>...] where:

•

-domain <domain_name_or_pattern> shows only AO configurations that are in domains with names matching one or more of the domain_name_or_pattern argument. This option does not allow listing objects within a domain of which the user is not a member. Patterns are glob-style (shell-style) patterns.

•

[<AOCFG_name>...|<pattern>...] specifies that AO configurations matching either the specified AO configuration name or those AO configurations matching the specified pattern are displayed. This specifier can be repeated to display information for multiple AO configurations. If not specified, all AO configurations in the system are displayed.

Modifying an Adaptive Optimization Configuration

To update an AO configuration, use the setaocfg command: cli% setaocfg [options <arg>] <AOCFG_name>

144 Adaptive Optimization

NOTE: Two or more tier CPGs must be present in an AO configuration at all times.

If domains are used, all CPGs must be either in the same domain or not in any domain.

A CPG can only belong to one AO configuration.

A CPG can be removed from a tier by specifying a null string "". At least two tiers must remain.

A CPG can be moved and swapped between tiers within the same AO configuration.

A CPG cannot be moved between AO configurations; it must first be removed from one and then added to the second.

Active use of Adaptive Optimization requires an Adaptive Optimization license. Contact your local

HP representative for information.

A maximum of two tier CPG settings can be modified in a single setaocfg command. This includes swapping CPGs between tiers or replacing up to two CPGs with new ones. A maximum of one

CPG can be removed from an AO configuration in order to maintain the minimum of two defined tier CPGs.

For example: cli% setaocfg -t0cpg tier0_R6_SSD -t1cpg tier1_R5_FC -mode Performance AOCFG_name where:

•

-t0cpg is the tier 0 CPG.

• tier0_R6_SSD is the tier 0 CPG name.

•

-t1cpg is the tier 1 CPG.

• tier1_R5_FC is the tier 1 CPG name.

•

-mode <mode> specifies one of the following optimization biases for the AO configuration:

◦

Performance

—Move more regions towards higher performance tier.

◦

Balanced

—Balance between higher performance and lower cost.

◦

Cost

—Move more regions towards lower cost tier.

•

—name <AOCFG_name> specifies a new name for the AO configuration (up to 31 characters in length).

In the following example, the optimization bias (that is, the mode) of an AO configuration aocfg1 is changed to Balanced.

CLI% setaocfg -mode Balanced AOCFG_name

In the following example, the tier 1 CPG for AO configuration aocfg2 is set to tier1_R5_FC2.

tier1_R5_FC2 must not already be used in an AO configuration, and the tier 1 CPG for aocfg2 must not already be set. Also, if domains are in use, the domain of R5FCcpg must match the existing tier CPGs, or have no domain if the other CPGs are not in a domain.

CLI% setaocfg -t1cpg tier1_R5_FC2 aocfg2

In the following example, a CPG is swapped between tier 0 and tier 2:

CLI% setaocfg -t0cpg tier1_R1_SSD2 -t2cpg tier2_R6_NL2 aocfg3

Modifying an Adaptive Optimization Configuration 145

In the following example, a CPG is removed from a tier, assuming that three tiers were initially created. If there are two tiers, this command is not permitted, because AO configurations require a minimum of two storage tiers.

CLI% cli% setaocfg -t0cpg "" aocfg1

Removing an Adaptive Optimization Configuration

To remove an AO configuration from the system, use the removeaocfg command: cli% removeaocfg [options] <AOCFG_name> where:

•

-pat <pattern> indicates that specified patterns are treated as glob-style patterns and that all AO configurations matching the specified pattern are removed. By default, confirmation is required to proceed with the command unless the -f option is specified. This option must be used if the pattern specifier is used.

This specifier can be repeated to remove multiple AO configurations. If this specifier is not used, the <AOCFG_name> specifier must be used.

•

-f specifies that the command is forced. If this option is not used, the command requires confirmation before proceeding with its operation.

•

<AOCFG_name> specifies the name of the AO configuration that is to be removed.

In the following example, AO configurations that start with test are removed without requiring user confirmation to remove them: cli% removeaocfg -f -pat test*

NOTE: A CPG that is part of an AO configuration cannot be removed from the system until either the AO configuration is removed or the CPG is removed from the aocfg.

146 Adaptive Optimization

15 HP Priority Optimization

During recent years, consolidation of storage systems has reduced complexity of data storage, delivering efficiency in management, occupied floor space, and energy consumption. However, the consolidation of many disjoint workloads into a single storage system also results in contention for shared system resources on the system.

Examples of such shared resources include front-end host Fiber Channel (FC), iSCSI and FCoE adapters, back-end FC or SAS disk connections, physical disks, data and control cache, ASICs,

CPUs, and backplane interconnections. Data packets arriving at the front-end FC HBA adapters are handled on a first-come, first-serve basis. On the surface, this may sound fair, but it can lead to unequal and inconsistent throughput for multiple concurrent workloads.

HP 3PAR’s Priority Optimization software manages and distributes the I/O capacity of an HP 3PAR

StoreServ Storage system across multiple workloads. The tool enables the co-location of the data of workloads of different types, such as sequential, random, online transaction processing (OLTP), with different I/O packet sizes on a single storage system while achieving adequate and stable performance in a multi-tenant environment.

Requirements

HP 3PAR Priority Optimization is supported on all HP 3PAR StoreServ Storage systems that are certified for HP 3PAR OS 3.1.2 MU2:

•

HP 3PAR StoreServ Storage F-Class

•

HP 3PAR StoreServ Storage T-Class

•

HP 3PAR StoreServ Storage 7000

•

HP 3PAR StoreServ Storage 10000

A valid license for HP 3PAR Priority Optimization is required on the HP 3PAR StoreServ Storage system. The HP 3PAR Priority Optimization has its own license key. The license is spindle-based, available a-la-carte and as part of the Data Optimization Suite v2 available for HP 3PAR StorServ

7000 and HP 3PAR StorServ 10000 systems. Consult your HP representative or authorized HP partner for more information on HP 3PAR Priority Optimization licensing.

Creating and managing QoS definitions requires the HP 3PAR MC 4.4 and later. To use the command line, you must install HP 3PAR CLI 3.1.2 MU2.

Reports on HP 3PAR Priority Optimization are available through HP 3PAR System Reporter 3.1

MU1 and later, and through the HP 3PAR MC 4.4 and later. The reports on the QoS definitions require a license for HP 3PAR System Reporter.

While QoS is in principle OS-agnostic, see the HP SPOCK website for the list of operating systems that are certified for use with HP 3PAR Priority Optimization: http://www.hp.com/storage/spock

Virtual Volume Sets

QoS rules operate on sets of VVs called VVsets. A VVset is an autonomic group object that is a collection of virtual volumes. VVsets help to simplify administration of volumes and reduce human error. An operation such as exporting a VVset to a host will export all member volumes of the

VVset. Adding a volume to the VVset will export the new volume automatically to the host or host set.

VVsets have a number of use cases beyond reducing administration for their volume members.

Most HP 3PAR Remote Copy operations are performed on sets of virtual volumes called remote copy volume groups. VVsets also enable simultaneous point-in-time snapshots of all volumes contained in the set with a single command. Up to 8192 volumes can be part of a VVset.

Requirements 147

VVsets are created in the MC or in the CLI. In the MC VVsets are co-created with new volumes, or created by using existing volumes.

Figure 2 (page 148)

shows the creation of VVset MS-SQL with member volumes MS-SQL.1, MS-SQL.2 and MS-SQL.3. At creation time, each volume member has the same provisioning type, user and copy CPG, allocation warnings, and volume size. Each of these settings can be changed afterwards.

Figure 2 VVset Creation at Time of Volume Creation

To ends the operation of creating volumes and their VVset, click Finish. The end result of VVset creation is shown in

Figure 3 (page 149)

148 HP Priority Optimization

Figure 3 VVset Creation

A VVset can also be created so as to contain existing virtual volumes. Right-click a Virtual Volume

Sets entry in the Provisioning tree of the MC, and then select Create Virtual Volume set (see

Figure 4 (page 149) ).

Figure 4 Creating a VVset from the Provisioning Tree

In the Create Virtual Volume Set dialog box, supply the name, and, optionally, the domain and comments for the new VVset (see

Figure 5 (page 150)

Virtual Volume Sets 149

Figure 5 Create Virtual Volume Set

Click Next to show the list of all VVs on the system (see

Figure 6 (page 150)

Figure 6 Adding Existing Volumes to a New VVset

Select the volumes you want to be a member of VVset (Test in this example) and click the yellow arrow pointing downward to add them to the VVset; then click the Next button to proceed.

As shown in

Figure 7 (page 151) , the VVset Test now has three member volumes.

150 HP Priority Optimization

Figure 7 Test VVset with Three Pre-existing Volume Members

To show a summary of the intended operation, click Next (summary window not shown).

To complete the VVset creation, click Finish on the summary screen or on

Figure 7 (page 151) . The

result is shown in

Figure 8 (page 151) : the Test VVset has been created with three previously

existing member volumes.

Figure 8 Test VVset with Three Members

The volumes in the VVset in

Figure 8 (page 151) have different RAID levels and sizes. VVsets can

contain volumes with different provisioning type, RAID level, size, and CPGs.

All volumes in a VVset can be exported in one step to hosts or host sets by right-clicking the name of the VVset (in

Figure 8 (page 151) , and then selecting the Export option in the menu that appears.

Applying Quality of Service Rules

HP 3PAR Priority Optimization software introduces quality-of-service rules to manage and control the I/O capacity of an HP 3PAR StoreServ Storage system across multiple workloads. Application of the rules enables co-location of the data from workloads of different types (such as sequential,

Applying Quality of Service Rules 151

random, and transactional, among others), with different I/O packet sizes on a single HP 3PAR storage system. The use of QoS rules stabilizes performance in a multi-tenant environment.

Mode of Operation

HP 3PAR Priority Optimization operates by applying upper-limit control on I/O traffic to and from hosts connected to an HP 3PAR StoreServ Storage system. These limits, or QoS rules, are defined for front-end input/output operations per second (IOPS) and for bandwidth.

NOTE: IOPS is a common performance measurement used to benchmark computer storage. It is indicative of how many host I/O requests the array is receiving per second. It is typically stated as a whole number, such as 50,000 IOPS.

QoS rules are applied using autonomic groups. Every QoS rule is associated with one (and only one) target object. The smallest target object to which a QoS rule can be applied is a virtual volume set (VVset). Because a VVset can consist of a single VV, a QoS rule can target a single VV.

Every QoS rule has four attributes:

Name The name of the QoS rule is the same as the name of the VVset.

State The QoS rule can be active or disabled.

I/O Limit

Bandwidth Limit

The limit on IOPS for the target object.

The limit in bytes-per-second transfer rate for the target object.

When an I/O packet reaches the HP 3PAR StoreServ controllers, HP 3PAR Priority Optimization takes one of the following actions:

•

Pass the I/O packet to the VV.

•

Delay the I/O by stalling it in a private QoS queue that gets processed periodically.

•

Return a SCSI queue-full (QFULL) message to the host.

If the upper limit for IOPS or bandwidth for a particular VVset has been reached, HP 3PAR Priority

Optimization delays SCSI I/O request responses for the volumes contained in that VVset. These delayed I/O requests are pushed onto an outstanding I/O queue for the VV(s) in the VVset experiencing the limit breach.

Every QoS rule maintains its own queue for delayed I/Os. These queues are constructed inside the each HP 3PAR StoreServ controller node that receives an I/O request that needs to be delayed.

Only the I/O request descriptions are queued, not the actual data. A controller node’s cache is not impacted, because the QoS rules are applied before write I/O data reaches the cache.

The size of a request queue varies by maximum delay time and QoS limits. When I/O requests reside longer than 200ms in a QoS queue, any more incoming I/Os to the volumes in the VVset are rejected, and a QFULL response is returned to the server using the volumes. QFULL prevents delayed I/O from holding all system resources, such as host, HBA, and VV layer buffers and queues. Hosts should respond to the QFULL message appropriately and throttle I/O. The I/O delay and the eventual QFULL response applies to all members of the VVset, even if only one of the VVs causes the QoS threshold breach.

HP 3PAR Priority Optimization features a system-wide, built-in QoS rule called all_others that is inactive by default. This rule limits the IOPS and/or bandwidth to all volumes and VVsets that are not subject to a named rule. Enabling the all_others rule obviates the need to define a specific, named rule for all workloads on the storage system.

QoS Rule Minimum and Maximum

HP 3PAR Priority Optimization sets the values for IOPS and bandwidth in QoS rules in absolute numbers, not in percentages. The IOPS number is stated as an integer between 0 and 2

-1, although a more realistic upper limit is the number of IOPS that the particular array in question is capable of providing, given its configuration. The value for bandwidth is stated as an integer

152 HP Priority Optimization

between 0 and 2

-1, expressed in KB/second, although a more realistic upper limit is the throughput in KB/second that the particular array in question is capable of providing, given its configuration.

NOTE: Throughput, also called bandwidth, is a measure of the amount of data processed by the array per unit of time. It is usually measured in MB/second.

QoS rules support specifying an IOPS upper limit, a bandwidth upper limit, or both. The iteration towards a new IOPS or bandwidth setting follows a damped exponential curve and is completed in a few seconds. During operation, HP 3PAR Priority Optimization samples the IOPS and bandwidth values per VVset every 8 ms, and assembles 625 of these periods into a moving 5-second averaged window to adjust the ingress of the I/O to the QoS cap that was set.

QoS Rule Actions

QoS rules are subject to five distinct actions:

Create A QoS rule is created.

Enable A disabled QoS rule is made active.

Disable

Change

An active QoS rule is made inactive.

The limit values for a QoS rule are modified.

Clear The QoS rule is removed from the system.

A QoS rule that is created becomes active immediately. This default behavior can be overridden when using the HP 3PAR CLI to create the rule; the HP 3PAR MC does not offer that option.

Changing one or both limit values in a QoS rule activates those values instantly on the VVset; there is no need to disable the QoS rule first. An active QoS rule can be removed without first disabling it.

Overlapping QoS rules

A VV can be a member of multiple VVsets, each of which can have a QoS rule defined. In such a case, the I/O to and from volumes in the VVset is governed by multiple, possibly overlapping rules. All active rules for a particular VVset are combined using wired-OR logic: the QoS limit that is reached first takes precedence. A QoS rule can be created on a VVset that has none, or not all, of its VVs exported to a host.

Minimum QoS Settings

HP 3PAR Priority Optimization provides no enforcement for minimum QoS levels. The minimum will be ensured, provided the system has been correctly sized for the expected total IOPS and throughput, and provided QoS rules against all VVsets were installed such that their combined sum does not exceed what the system is capable of delivering.

QoS on Copied Volumes

Virtual and physical copies of VVs in a VVset are not automatically a member of the parent VVset; they have to be added manually to the parent VVset in order to be governed by the same QoS rules. Virtual and physical copies can be subject to a different QoS rule than their parent VV, if desired. QoS rules are persistent across a reboot of a HP 3PAR StoreServ Storage system. A VVset cannot be removed unless all QoS rules defined for it are removed first.

Applying Quality of Service Rules 153

QoS Metrics

With HP 3PAR MC 4.4 and later, new charts showing historical data about how QoS operates for a particular VVset are available. To view the charts, click the Performance and Reports tab in the MC. The charts cover the following data:

•

IOPS

•

Bandwidth

•

Service time

•

I/O size

•

Rejected packets

•

Queue length

HP 3PAR Priority Optimization includes only host I/O in its decisions to delay or reject I/O packets.

I/O traffic for remote copy, online import, or over the peer links of peer motion, does not influence the I/O statistics.

Using HP 3PAR Priority Optimization

You can manage HP 3PAR Priority Optimization either through the HP 3PAR MC, or through the

HP 3PAR CLI. This section describes procedures and best practices.

Creating a New QoS Rule

Creating a New QoS Rule with the HP 3PAR CLI

To create a new rule for a VVset using the MC, select and right-click the VVset name in the Virtual

Volume Sets tree node in the Provisioning pane. A popup menu with configuration options appears

(see

Figure 9 (page 154) ). If this is a new rule, only the Configure QoS option is available.

Figure 9 Configuring a New QoS Rule

Click Configure QoS. The Target Type defaults to Virtual Volume Set, since in this case QoS creation started out from a VVset. The Configure QoS dialog box appears.

154 HP Priority Optimization

Figure 10 Configure QoS

Enter non-negative integer values either for I/O Limit (IOs/Sec), within a range of 0–2

Bandwidth Limit (KBs/Sec), within a range of 0–2

-1, and then click OK.

-1, or for

When a QoS rule is configured, it becomes active immediately. If values for the I/O limit, bandwidth limit, or both were defined previously, you can right-click the VVset name for a menu option to configure, clear, or disable the rule, as shown in

Figure 11 (page 155)

Figure 11 Configuration Options for Existing QoS on a VVset

You can change the values and save the rule by clicking OK. Changes made to an enabled QoS rule take effect immediately.

Creating a New QoS Rule with the HP 3PAR MC

The Provisioning tree, in the HP 3PAR MC for an HP 3PAR StoreServ Storage system that has a

QoS license, has a new tree node labeled QoS. The table to the right of the QoS tree node lists the configured QoS rules in the system, with their details (See

Figure 12 (page 156) ).

Using HP 3PAR Priority Optimization 155

Figure 12 QoS Tree Node

Right-click the VVset Name to open the same Configure QoS dialog box shown in the HP 3PAR

CLI (see

Figure 17 (page 158) ).

For an inactive rule, the Enable QoS option shown in

Figure 12 (page 156)

becomes available.

With the QoS node selected in the Provisioning manager, you can also initiate QoS rule configuration from the icons shown in the highlighted portion of

Figure 13 (page 156)

Figure 13 QoS Configuration Icons

With the Virtual Volume Sets node selected in the Provisioning tree, you can click the QoS icon, highlighted in

Figure 14 (page 157)

, to configure a particular QoS rule.

156 HP Priority Optimization

Figure 14 VVset Icon for QoS Configuration

For VVset QoS configuration, the Target Type field in the Configure QoS dialog box has a second value, System (see

Figure 15 (page 157) ).

Figure 15 System Target Type in Configure QoS Dialog Box

A System target-type rule governs all VVsets and VVs that are not subject to explicit QoS rules.

You must be very careful when defining the limits for the ‘System Target Type. To ensure that at least some IOPS and bandwidth is available to all the volumes under this rule, HP 3PAR Priority

Optimization enforces a minimum value for the I/O limit of 1000 IOs/sec and 100,000 KBs/sec for the bandwidth limit, although these limits may be far too low for some environments. If lower values are entered, a popup message appears, showing information about the minimum values, and closes the configuration window. If the System QoS rule is configured, its defined values will show up in the configuration window, and changes can be made to it.

Figure 16 (page 158)

shows how the System target is displayed in the QoS tree in the Provisioning pane in the HP 3PAR MC.

Using HP 3PAR Priority Optimization 157

Figure 16 System Target in QoS Tree

Viewing a QoS Rule

To display the current values of an existing QoS rule, select Configure QoS. The Configure QoS dialog box displays current values (see

Figure 17 (page 158) ).

Figure 17 QoS Current Values

Modifying a QoS Rule

Three new CLI commands are available to create and manage QoS rules. The commands and their syntax details are:

• setqos [options] [{vvset:{<name>|<pattern>}|sys:all_others}]...

The seqqos command creates and updates QoS rules in a system.

• showqos [options] [{vvset:{<name>|<pattern>}|sys:all_others}]...

The showqos command lists the QoS rules configured in a system.

• statqos [options] [{vvset:{<name>|<pattern>}|sys:all_others}]...

The statqos command displays run-time statistics of active QoS rules.

For details about command syntax and the columns in their output, see the HP 3PAR CLI Help page for each of the commands.

158 HP Priority Optimization

The integer value for bandwidth in the setqos command can optionally be followed with:

• k or K to indicate a multiple of 1000

• m or M to indicate a multiple of 1,000,000

• g or G to indicate a multiple of 1,000,000,000

If you specify "none", there is no limit on I/O issue bandwidth rate.

The CLI offers a number of features that are not available in the MC. For example, a QoS rule can be created with the setqos command and be kept inactive by using the -off option.

All user-defined rules can be switched off simultaneously by using the setqos –off vvset:* command; use the setqos –on vvset:* command to enable them again.

Rules can be shown in ordered form by issuing the showqos –sortcol X,[inc|dec], where

X is the column number, and inc and dec sort on increasing or decreasing values in the column, respectively. Column counting in the output of showqos starts with the left column, which is numbered 0.

Figure 18 (page 159)

shows output of the showqos command, with the sorting option set on decreasing IOPS value.

Figure 18 Showqos Command Output

An option of particular interest for setqos is –vv <name>|<pattern>. This option changes the QoS rule, for all VVsets that include VVs with names matching any of the names or patterns specified, to the value contained in the setqos statement. If a VV is in a VVset for which no QoS rule has yet been defined, a new rule is created with the limits in the setqos command.

The built-in rule all_others is switched off by the command setqos –off sys:all_others.

The showqos and statqos command provide a centralized view of the QoS rules in the systems and how the workloads conform to them.

Executing the QoS CLI commands requires a logon to an account with Super or Edit rights. Any role granted the qos_set right can set QoS configurations. QoS rules can be scheduled using the createsched command for automated QoS policy changes for example to adapt to day/night or weekday/weekend workload conditions.

Another new HP 3PAR CLI command, srstatqos, displays historical performance data reports for the QoS rules. This command is integrated in HP 3PAR System Reporter (SR) on the 3PAR nodes.

SR 3.1 MU1, installed on a separate server, includes statistics on QoS. To learn more about the

QoS information in SR, see the HP 3PAR System Reporter 3.1 Software User's Guide and the HP

3PAR System Reporter 3.1 Software Release Notes.

Removing a QoS Rule

To remove a QoS rule, click the Clear QoS option (see the menu in

Figure 11 (page 155)

). Clearing a QoS rule does not require first disabling the rule.

The Disable QoS option deactivates an enabled rule. When the rule for a VVset is disabled, the

Enable QoS selection (see

Figure 11 (page 155)

) becomes active.

Using HP 3PAR Priority Optimization 159

A QoS rule can be enabled and disabled at any moment. Once a QoS rule is disabled, the IOPS and bandwidth for the VVs in the VVset increases (if they were being delayed by the rule).

Managing QoS Rules

There is no limitation on the minimum number of IOPS and bandwidth that can be set on a giving

VVset QoS Rule. It is important that the workloads of the various applications be fully understood before applying a QoS rule. HP 3PAR System Reporter can be used to make this determination.

The following best practices provide general guidelines only; details are beyond the scope of this paper.

Assembling VVs into VVsets

VVsets group virtual volumes logically. Use cases for VVsets include taking simultaneous point-in-time virtual copies of multiple volumes, and creating Remote Copy volume groups for write consistency during replication operations.

Volumes that belong together because they are owned by the same application or because they belong in the same virtual domain should be included in the same VVset. Even if a number of virtual volumes are unrelated and do not need write consistency, you can group them to a VVset so as to reduce the administrative overhead when managing them. This way the I/O profile of the volumes can be managed by a single QoS rule for their parent VVset.

VVsets are especially useful in the deployment of HP 3PAR Priority Optimization, because QoS rules in HP 3PAR Priority Optimization are defined on VVsets. HP strongly encourages the creation of VVsets and group volumes logically on HP 3PAR StoreServ storage systems, if this is not yet a common practice anway.

Determining the Values for IOPS and Bandwidth for a System

HP 3PAR Priority Optimization’s QoS rules define limits for IOPS and bandwidth in absolute numbers, not percentages. Because of this, the QoS administrator needs reasonably accurate data on the system’s maximum I/O and throughput capability. He also requires an accurate understanding of actual I/O and throughput workloads exercise to the volumes that will have QoS applied to them.

HP Presales can estimate the maximum front-end workload for a system in IOPS and bandwidth, assuming a particular I/O size and a given ratio for read/write I/Os. With this information, QoS rules can be defined per workload, ensuring that the total sum of IOPS or bandwidth does not exceed what is sustainable by the system configuration if no oversubscription is allowed. Re-analysis of the system’s capability and re-adjustments of the limit values for any existing QoS rules must take place in the following cases:

•

When upgrading the storage system with additional disk drives and/or nodes.

•

When making use of additional FC and/or iSCSI interface cards to the storage system.

•

When adding additional physical hosts of virtual machines with extra workloads to the storage system.

•

When upgrading the host hardware to a newer generation that offers more CPU power and/or memory (for example, from G6 to Gen8 Proliant blades), generating more IOPS and bandwidth, or when hardware details change in a virtualized server environment.

•

When deploying a new generation of an operating system on the host like moving from

Windows Server 2003 to the Windows Server 2008 or Windows Server 2012 version, or when moving from a 32-bit to 64-bit environment.

•

When deploying a new brand of generation of FC or iSCSI HBAs on the host that have specific queue depth requirements.

160 HP Priority Optimization

NOTE: Queue depth is the average number of I/O jobs, either processing or waiting to be processed, within a polling interval. The queue depth is a non-negative integer number.

•

When upgrading the end-to-end SAN pathing from 4 Gb/sec to 8 Gb/sec.

In general, HP recommends review of the system I/O capability and adjustment of the QoS rules in use whenever a change was made to one part of the entire chain from the host to the HP 3PAR

OS.

Handling Tier-1 Applications

The HP 3PAR StoreServ storage systems are Tier-1 arrays that can handle multiple mission-critical workloads concurrently, as opposed to workloads of medium importance and performance requirements. Tier-1 applications should be given all resources they need during runtime, given their vital business impact.

HP recommends that a QoS rule be defined with sensible limits for IOPS and bandwidth on all

VVsets that have a known I/O profile. The System rule should be defined to control all volumes created on the system that do not have an explicitly defined QoS rule.

If you don’t set a QoS rule, and the all_others rule is active, mission-critical applications will be subject to the all_others rule. To prevent the System rule from controlling the Tier-1 applications, define a QoS rule with very high values for IOPS and bandwidth. This way, the mission-critical workload will be able to consume the I/O resources they need to perform optimally.

Implementing the System Rule

Workloads without a QoS rule consume I/O resources in an uncontrolled manner and may starve those that are subject to a QoS rule. To ensure an acceptable level of performance across all applications on a storage system if QoS is used, all volumes must be part of a QoS rule with meaningful limits reflecting the application’s I/O requirements. The System QoS rule should be enabled and a value specified for its maximum IOPS and bandwidth to control the I/O traffic from

VVs and VVsets not subject to a specific QoS rule. This prevents any new volumes added to the

HP 3PAR StoreServ or existing ones that are not subject to a QoS rule from negatively affecting the entire system overconsuming IOPS or bandwidth.

As explained in

“Creating a New QoS Rule with the HP 3PAR MC” (page 155) , the default minimum

allowed values for the System rule are 1000 for the I/O Limit and 100,000 KB/sec for the bandwidth limit. Be sure to change these to acceptable values if the defaults are deemed too small.

Overprovisioning the System

HP 3PAR Priority Optimization allows over-provisioning when creating QoS rules: rules whose combined value for IOPS or bandwidth can exceed the I/O capacity of an HP 3PAR StoreServ.

This is an established practice if the workloads are sufficiently orthogonal in their I/O usage.

For example, a database used only during the day time and a backup application running only during the night can each be given the entire I/O capacity of the system in their respective QoS rules. When overprovisioning concurrent workloads, QoS prevents a single application or customer from monopolizing the system.

For another example, a system capable of 50 k IOPS could have 10 customers, each limited to

10 k IOPS. The system is over-provisioned for IOPS, but no single customer can monopolize the system. Continuous monitoring of system performance by HP 3PAR System Reporter is mandatory to ensure that every application and customer performs well without reaching their I/O limits.

QoS Influence on the Host Side

The QoS rules in HP 3PAR Priority Optimization specify the relative importance of the I/O of each workload on the storage system. When the IOPS or bandwidth demand of an application reaches the implemented QoS limits, the performance of the application on the host will no longer grow.

Using HP 3PAR Priority Optimization 161

Lowering the QoS cap will result in higher I/O response times and reduced throughput on the host, and eventually queue-full errors are returned by the array to the host.

NOTE: Response time is the average measured time that it takes the array to process an I/O request. On HP 3PAR StoreServ Storage systems, response time may be reported as “service time.”

Response time is measured in milliseconds.

On the other hand, a lowered QoS cap for one workload will free I/O resources on the host, which in turn may reduce memory and CPU cycle consumption to the benefit of other workloads.

HP 3PAR Priority Optimization can control host-side resources, obviating the need to define QoS and metrics in a workload manager tool on the host. However, host-side and storage system QoS rules can be combined for tighter control, or when memory and CPU cycle consumption management is required on the host.

Maximum Number of QoS Rules per VV

A given VV can be part of a large number of VVsets. HP does not recommend application of multiple QoS rules to the same VV. For this reason, QoS rules can be defined on a maximum of eight VVsets that contain a particular VV. The lowest value for IOPS and bandwidth, for a VVset that hosts a VV, imposes its limits on the I/O traffic to and from the VV.

QoS on a Subset of VVset Volumes

By default, a QoS rule on a VVset governs all volumes in the set; but only a subset of the volumes in the VVset might need a QoS rule. In this situation, create a second VVset that contains only the volumes that need a QoS rule, and then define the rule. The volumes in the second VVset do not need to be exported for the QoS rule to take action.

If the System rule is defined, it takes action on all VVsets for which a QoS rule has not been defined. If at least one volume of the VVset has a QoS rule defined in another VVset, the named

QoS rule takes precedence over the System rule, even if the named QoS rule has a lower value for IOPS or bandwidth.

Application Interoperability

HP 3PAR Priority Optimization sets and manages QoS rules defined on I/O traffic that enters and leaves an HP 3PAR StoreServ meaning on the front-end host ports of the array. Software products for HP 3PAR StoreServ storage systems, such as Dynamic Optimization (DO), Adaptive Optimization

(AO), Virtual and Physical Copy, HP 3PAR System Reporter, the Thin Provisioning Suite, and the

Recovery Manager packages work on data in the backend. This means they are all compatible and operate transparently to HP 3PAR Priority Optimization. HP 3PAR Peer Motion traffic over the

Peer ports can be the subject of a QoS rule on the source HP 3PAR StoreServ Storage system.

Databases

All database software vendors recommend that you separate data files, index files, and transactional and archive logs on separate volumes. The write capability and location of the online transaction logs are most important as the entire performance of the database depends on the writes to these logs. For this reason a QoS rule on the volumes containing the online transaction logs should be carefully dimensioned to not inhibit the performance of the database. QoS rules on the I/O performance of the database volumes will take care of runaway queries that consume lots of IOPS and bandwidth. Databases at many customers are a considered mission-critical application and putting a QoS rule on them should never inhibit their normal operation.

Microsoft Exchange

Microsoft Exchange Server is a scalable, commercial mail server that supports thousands of users per instance. As a general practice, it is recommended that the mailbox database files and the log files be separated onto different volumes. The databases can be spread over multiple volumes as well. Using a QoS rule, to limit the IOPS and/or bandwidth to the volume sets for the mail

162 HP Priority Optimization

database of a particular group of users, enhances the performance stability for mail databases for other users and for other applications on the HP 3PAR StoreServ Storage systems.

Microsoft Exchange is a highly interactive software, and its users demand a swift response to mouse clicks in the Outlook client. To prevent Microsoft Exchange from reporting errors, be careful to ensure that volumes receive enough IOPs and throughput so that the Microsoft Exchange server delivers sufficiently low I/O response times.

Virtualization Software

Virtualization platforms, such as VMware vSphere and Microsoft Hyper-V, make use of container files to store one or more virtual hard disk drives used by virtual machines. Each container file is built on one or more LUNs accessed over a SAN. Adding the LUNs that make up the container file to a VVset permits application of a QoS rule. This rule will control the IOPS and/or bandwidth for all virtual machines (VMs) whose virtual hard drives are carved out of that LUN. Be careful to ensure that there is enough bandwidth and IOPS in the QoS rule, so that the applications running on the VMs can deliver acceptable I/O response times.

QoS I/O control operates on all VMs sharing a VMware datastore and, in some cases, this level of control may not be granular enough. Recent versions of VMware offer three native types of I/O resource control. Their characteristics, together with those of QoS, are listed in

Table 16 (page

163)

Table 16 VMware I/O Resource Control

VMware Storage DRS

VMware SIOC

VMware AQD

Control Mechanism HP 3PAR QoS

I/O control technique: Limit IOPS and bandwidth

Reacts on:

Granularity:

Managed from:

Availability:

None

All VMs in datastore

HP 3PAR MC

HP 3PAR OS 3.1.2

MU2

Migrate VM to other datastore

Control queue depth of datastore SAN LUN in VMkernel; VM shares enforced

Control queue depth of datastore SAN LUN in VMkernel

I/O latency and space utilization

I/O latency

Single VM

VMware vSphere

All VMs in a single datastore

VMware vSphere

Queue Full or Device

Busy at LUN or port level

All hosts using the

SAN LUN for the datastore or a particular port on the

3PAR

VMware vSphere vSphere 5.0 and later with Enterprise Plus license vSphere 4.1 and later with Enterprise Plus license vSphere 3.5 U4 and later with Standard license

1, 2, 3

Distributes Resource Scheduler

Storage I/O Control

Adaptive Queue Depth

HP 3PAR Priority Optimization QoS rules operate on volumes inside VVsets on an HP 3PAR StoreServ system. QoS rules are agnostic for the application type they manage. A QoS rule, on a VVset that contains one or more VVs that make up a datastore, controls the I/O across all VMs using that datastore. This could be suboptimal, however, as some VMs need more I/O resources than others.

Combining QoS with SIOC offers I/O control up to the level of an individual VM—an I/O share and an optional IOPS limit defined per VM distribute the available I/O capacity in a fair way across VMs, ensuring that no single VM consumes all the I/O provided to the VVset through QoS settings. Note that SIOC will not respond to queue-full messages from QoS directly.

HP 3PAR Priority Optimization can also cooperate with AQD to manage I/O. AQD handles I/O congestion in the I/O path to the datastore LUN. It does so by halving the queue length to the LUN

Using HP 3PAR Priority Optimization 163

when a queue-full message arrives at the ESXi host. This reduction in the queue length gives the array an opportunity to decrease the number of outstanding I/Os at its end. In vSphere 5.1 U1,

AQD can be configured by LUN, or globally for the ESXi host.

Combining QoS rules with SIOC and ADQ provides I/O congestion control on three different levels: the workload will honor the QoS limits, and it will be impacted indirectly when SIOC reacts to latency increases and when AQD responds to queue-full messages from QoS rules. Coordination and some experimenting may be necessary to deliver the best results.

VMware Storage DRS, a new feature introduced in VMware vSphere 5.0, groups datastores into a cluster so that they are managed as a single unit. This allows for load balancing VMs across datastores based on I/O latency and space utilization in an automated or manual way. Storage

DRS leans on Storage vMotion for migrating VMDKs to different datastores. Combining HP 3PAR

Priority Optimization with Storage DRS requires careful planning of the QoS rules. A QoS rule governs one or more LUNs that make up a datastore. Storage DRS implies a source and a destination datastore, each possibly subject to a QoS rule. The QoS rule if any on the Storage

DRS destination datastore should have enough headroom to accommodate the additional I/O capacity of the migrated VMDK. If the workload’s I/O characteristics are not very well known, HP recommends manual Storage DRS migrations over automated ones to detect any I/O congestion due to the migration in an early stage.

Reporting

Continuous performance monitoring of all critical parameters of a storage system is essential in managing a storage system. HP 3PAR Priority Optimization features new charts in the HP 3PAR

MC for monitoring QoS rules graphically over time. For example,

Figure 19 (page 164)

shows a graph of the behavior for a number of VVsets with their respective QoS rule and the all_others rule over a period of time.

Figure 19 Historic Behavior of QoS Rules on System

Use the HP 3PAR CLI command statqos to display run-time statistics of active QoS rules in columns. The command produces output every 2 seconds; this interval can be changed. Depending on the active QoS rule, values for the following parameters are displayed:

•

IOPS

•

Bandwidth

164 HP Priority Optimization

•

Service time (Svt_ms)

•

Wait time (Wtt_ms)

•

Size of the I/O requests (IOSz_KB)

•

Number of rejected I/O requests (Rej)

•

Averaged QoS queue length (Qlen)

•

Averaged wait queue length (WQlen)

Figure 20 (page 165)

shows sample output for the statqos command.

Figure 20 Run-time Statistics Shown by the statqos Command

The column headers in

Figure 20 (page 165)

show:

Type

QoS target type (vvset or sys)

Name

I/O_per_second

QoS target name; also the name of the VVset on which the rule is defined

IOPS cap, set by the user

Cur

Current IOPS

Avg

Average IOPS over all iterations of the statqos command so far

Max

Maximum IOPS over all iterations of the statqos command so far

Kbytes_per_second

Svt_ms

Wtt_ms

IOSz_KB

Rej

WQlen

IOPS cap, set by the user

Cur

Current IOPS

Avg

Average IOPS over all iterations of the statqos command so far

Max

Maximum IOPS over all iterations of the statqos command so far

Total service time of I/Os processed by QoS (including wait time and the real service time)

Wait time of I/Os delayed by QoS

I/O block size in KB (1 KB = 1000 bytes)

Number of I/Os rejected by QoS

Number of I/Os delayed by QoS

Using HP 3PAR Priority Optimization 165

Qlen

Number of I/Os processed by QoS (including the number of I/Os delayed by QoS and number of I/Os processed by QoS without delay)

You can filter by VVset by using the srstatvlun command. This can be useful in determining which VVs in a given VVset contribute the most in reaching the QoS limit.

Using the statqos interface, the On-Node tool in HP 3PAR System Reporter samples QoS statistics periodically, and stores this information for all active QoS rules. The srstatqos command will report the statistics for the QoS rules for one or more VVsets for any desired time window. The high resolution sampling extracts QoS statistics data in 5–minute periods. srstatqos options mirror the options of other srstat commands.

Event Management

There is no mechanism to alert storage administrators of rejected I/O requests. Instead, monitor the QoS rules as described in

“Reporting” (page 164) . The debug event logs will show QFULL

messages for rejected I/O requests if they occur. To display the debug event log, issue the following

HP 3PAR CLI command:

# showeventlog –debug –msg Qfull

The following example shows a rejected I/O request:

Time : 2013-06-03 14:04:23 CEST

Severity : Debug

Type : Host error

Message : Port 0:1:1 -- SCSI status 0x28 (Qfull) Host:ireland.bel.hp.com (WWN

50060B0000C26612) LUN:2 LUN WWN:60002AC000000000000000AC000009AD VV:0

CDB:28002552AA4000002000 (Read10) Skey:0x00 (No sense) asc/q:0x00/00 (No additional sense information) VVstat:0x00 (TE_PASS -- Success) after 0.000s (-) toterr:9720, lunerr:2

166 HP Priority Optimization

16 Using the HP 3PAR SNMP Infrastructure

Overview

In addition to managing the system with the HP 3PAR CLI, the HP 3PAR OS includes an SNMP agent that allows you to perform some basic management functions via network management software running on a management station. These SNMP management functions require that you have SNMP management software not provided by HP. For information about SNMP, see the HP

3PAR StoreServ Storage Concepts Guide.

The HP 3PAR SNMP Agent

The HP 3PAR SNMP agent runs on the system and provides a management interface to enable other software products to manage HP hardware using SNMP. The HP 3PAR SNMP agent responds to GET, SET, GETNEXT, and GETBULK SNMP requests and also generates notification messages

(traps) for critical events (alerts) and alert state changes (for information about requests and traps, see the HP 3PAR StoreServ Storage Concepts Guide). These traps include the same information as the alerts described in the HP 3PAR OS Messages and Operator’s Guide.

The HP 3PAR SNMP agent supports SNMPv3, SNMPv2c, SMI-v2 standards, and the SNMPv2-MIB and a proprietary HP 3PAR MIB. For detailed information about these standards and MIBs, see the HP 3PAR StoreServ Storage Concepts Guide.

Locating the HP 3PAR MIB

The HP 3PAR MIB is located on the HP 3PAR CLI and SNMP CD.

alertNotify Traps

All alerts generated by the system, as well as all alert status change events, are translated into alertNotify traps. For information about system alerts, go to http://www.hp.com/support/ hpgt/3par and select your server platform.

NOTE: If you receive a trap with messageCode == 1245186, this is to notify you that an alert has changed state. In order to find out which alert has changed state, you must extract the alert

ID from the id trap field.

See the HP 3PAR StoreServ Storage Concepts Guide for additional information about alertNotify traps.

Registering an SNMP Manager

For detailed information about all HP 3PAR CLI commands described in this section, see the HP

3PAR Command Line Interface Reference for additional information and examples.

To register the SNMP manager with the agent, use the setsnmpmgr command followed by the manager’s IP address. If you need to use one of the following options, enter it after the command and before the IP address:

•

-p <port_number>

—Specifies the port number where the manager receives traps. The default port is 162.

•

-pw <password>

—Specifies the manager’s access password, if the manager has one.

•

-r <number>

—Specifies the number of times the system will attempt to resend the trap if the manager is not available. You can specify from 1 to 15 retries. The default is 2.

•

-t <seconds>

—Specifies the number of seconds to wait between retries. You can set this timeout interval from 1 to 300 seconds. The default is 200.

NOTE: The HP 3PAR OS supports a maximum of 10 registered SNMP managers.

Overview 167

Viewing Registered Managers

Use the HP 3PAR CLI command showsnmpmgr to see which managers are already registered with the SNMP agent.

NOTE: If the manager that monitors the system has changed, remove the old manager and register the new one.

Removing a Manager

To remove a manager from the agent’s list of registered managers, thus preventing that manager from receiving traps, use the removesnmpmgr command. If there is more than one manager running on the same server, you can distinguish between them by using the -p option followed by the port to which the manager is listening. Follow the command (and the option and its argument, if applicable) with the IP address of the manager’s server. For more information about the removesnmpmgr command, see the HP 3PAR Command Line Interface Reference.

Agent Community Strings

In order for the SNMP Manager to communicate with the HP 3PAR SNMP agent, it must pass the agent the correct community string. To do this, the manager needs to know the agent community string. The system comes with the single default community string “public” with reading permissions for the agent. You can add read-only and write-only community strings, and you can change or remove any of the community strings.

To see community strings that are currently available on the system, use the HP 3PAR CLI command showsnmppw

. By default, this command shows the read/write community string. If the community string you are requesting does not exist, you will get an error message.

To add or update a community string, use the setsnmppw command followed by the new community string. By default, this command changes the read/write community string.

To remove a community string, use the removesnmppw command. Once the community string is removed, the manager can no longer send requests to the SNMP agent. By default, this command removes the read/write community string.

For any of these three HP 3PAR CLI commands (showsnmppw, setsnmppw, and removesnmppw), you can follow the command with one or more of the following options to specify the community string to which the command applies:

•

-r for the read-only community string.

•

-w for the write-only community string.

•

-rw for the read/write community string.

Testing SNMP Managers

To send a test trap to all SNMP managers displayed with the showsnmpmgr command, issue the checksnmp command. The CLI displays the IP addresses of the tested mangers.

For details about the test trap sent by the checksnmp command, see the HP 3PAR Command Line

Interface Reference and the HP 3PAR CLI Help.

Creating SNMPv3 Users

To create SNMPv3 users you must have Super role user rights, or any role that has been granted the snmpuser_create right. The createsnmpuser command creates the SNMPv3 user secret key, which is used for generating authentication and privacy keys. The user name must be an existing HP 3PAR OS local user.

168 Using the HP 3PAR SNMP Infrastructure

To create an SNMPv3 user, issue the createsnmpuser -p <password> <user_name> command, where:

•

<password> represents the password of the HP 3PAR OS local user. The password is converted to an SNPMv3 secret key. If a password is not specified with the -p option, the system prompts you to enter the password of the local user.

•

<user_name> represents the HP 3PAR OS local user name. This user name is used as the

SNMPv3 user name.

You can verify the creation of a new user by using the showsnmpuser command.

For more information about the createsnmpuser command, see the HP 3PAR Command Line

Interface Reference.

Viewing SNMPv3 Users

To display information about SNMPv3 users and privacy protocols, use the showsnmpuser command:

•

To display all the SNMPv3 users of a system, issue the showsnmpuser command.

•

To display information for a specific showsnmpuser user, issue the showuser <user_name> command, where <user_name> is the name of the user.

NOTE: Users with Browse or Service roles are limited to viewing the information for their own accounts.

For more information about the showsnmpuser command, see the HP 3PAR Command Line

Interface Reference.

Removing SNMPv3 Users

After an SNMPv3 user is removed with the removesnmpuser command, an SNMPv3 manager can no longer use that user name to send requests to the SNMP agent. The HP 3PAR OS local user name remains valid unless it is removed with the removeuser <user_name> command. Removing a local user name with the removeuser command also removes the SNMPv3 user name from the system.

To remove an SNMPv3 user from the system, issue the removesnmpuser <user_name> command, where <user_name> is the name of the user.

You can verify the removal of a user with the showsnmpuser command.

Modifying SNMP Versions

Use the setsnmpmgr command to change properties associated with a previously configured

SNMP manager.

Viewing SNMPv3 Users 169

17 Using mySnapshot

Overview

This chapter describes how to use the mySnapshot utility. The mySnapshot utility enables safe and easy copy and provisioning access to non-storage professionals such as DBAs, software developers, and test engineers working with systems. Users can safely and easily restore their own copies of test data in seconds, without relying on the storage administrator.

About mySnapshot

mySnapshot is a copy utility that uses an access control list to associate a user with certain administrative rights and specified storage resources. Once these administrative rights are granted for the specified resources, the user can easily replace and restore copies of their own test database with the HP 3PAR CLI updatevv command. This enables users who normally only have Browse rights on the system to be able to update specific snapshots with more recent snapshots, a right usually only permitted for users with less restrictive roles. This enables faster results for developers who need to have their snapshots refreshed and reduces the workload for storage administrators.

See

“Learning About User Accounts” (page 16)

for more information about user roles and rights.

Setting Administrative Rights

To enable a user to easily replace and restore copies of a test database using mySnapshot, it is necessary to set administrative rights for that user. Administrative rights are set with the HP 3PAR

CLI setuseracl command. In order to use this command, you must have at least an Edit rights.

For additional details, see

“Learning About User Accounts” (page 16) .

The following example shows how to set administrative rights for user testuser1 to allow testuser1 to update copies of virtual volumes test.rw1 and test.rw2: cli% setuseracl testuser1 updatevv test.rw1 test.rw2

This command sets the access control list (ACL) for user testuser1, therefore enabling this user access to the updatevv command for the specified volumes only (in this example, test.rw1

and test.rw2). The updatevv command is described further in the following section,

“Replacing

Virtual Volume Snapshots” (page 170)

NOTE: In place of the specific virtual volume names used in the above example, it is also possible to specify a pattern. See the HP 3PAR Command Line Interface Reference for additional details.

You can view current administrative rights for all users with the showuseracl command as follows: cli% showuseracl

User Operation Object_Names_or_Patterns

testuser1 updatevv test.rw1, test.rw2

testuser2 updatevv avvro*

Replacing Virtual Volume Snapshots

A user with the appropriate rights set (see

“Setting Administrative Rights” (page 170)

) can use the updatevv command to replace a copy of a test database.

CAUTION: It may be necessary to unmount the filesystems on the host before replacing snapshots with mySnapshot. When replacing snapshots, the system automatically removes volume exports.

Some hosts may not react gracefully when volume exports are unexpectedly removed.

170 Using mySnapshot

NOTE: The updatevv command can also update sets of virtual volumes. For a complete list of options available for the updatevv command, see the HP 3PAR Command Line Interface Reference and the HP 3PAR CLI Help.

Replacing a Read-Only Snapshot

The following example shows how to replace a read-only snapshot volume with a new read-only snapshot volume.

In this example:

• test is a base volume (or a read-write snapshot). This volume holds the database.

• test.ro

is a read-only snapshot of test. This snapshot is a read-only copy of the database.

• testuser1 is a user with updatevv rights for volume test.ro. See

“Setting Administrative

Rights” (page 170)

for instructions on setting rights for replacing a read-only snapshots.

When test.ro needs to be updated, testuser1 unmounts the filesystem on the host and then issues the following HP 3PAR CLI command to replace test.ro with a new read-only copy: cli% updatevv test.ro

This command removes test.ro and replaces it with a new read-only snapshot of test. This new volume is also called test.ro.

NOTE:

In this example, test.ro can have a VLUN associated with it. The command will remember the

VLUN, remove the old snapshot, create a new snapshot, and recreate the VLUN with the new snapshot.

After the snapshot is replaced, testuser1 must remount the filesystem on the host.

Replacing a Read-Write Snapshot

The following example shows how to replace a read-write snapshot volume with a new read-write snapshot volume.

In this example:

• test is a base volume (or a read-write snapshot). This volume holds the database.

• test.ro1

is a read-only snapshot of test. This snapshot is the reference copy of the database.

• test.rw1

is a read-write snapshot of test.ro1. This is a snapshot of the reference copy of the database, created for development purposes.

• testuser1 is a user with updatevv rights for volume test.rw1 See

“Setting Administrative

Rights” (page 170)

for instructions on setting rights for replacing a read-write snapshots.

•

When test.rw1 needs to be restored, testuser1 unmounts the filesystem on the host and then issues the following HP 3PAR CLI command to replace test copy test.rw1 with a new copy: cli% updatevv test.rw1

This command removes test.rw1 and replaces it with a new snapshot of test.ro1. This new volume is also called test.rw1.

Replacing Virtual Volume Snapshots 171

NOTE:

In this example, test.rw1 can have VLUNs associated with it. The command will remember the

VLUN, remove the old snapshot, create a new snapshot, and recreate the VLUN with the new snapshot.

After the snapshot is replaced, testuser1 must remount the filesystem on the host.

In the above example, the replaced copy (test.rw1) is a new copy of the database made from the reference copy (test.ro1), and not from the database itself (test).

To get an up-to-date read-write copy of the original database, testuser1 must have updatevv rights for volumes test.rw1 and test.ro1. Unmount the filesystem on the host before issuing the following HP 3PAR CLI command: cli% updatevv -ro test.rw1

This command removes test.rw1 and test.ro1, and replaces them with a new read-only snapshot of test called test.ro1 and a new read/write snapshot of test.ro1 called test.rw1

. This gives the user an up-to-date read-write copy of the original database by creating a new read-only snapshot of the original in addition to the new read-write copy.

NOTE:

In this example, only the read-write snapshot (test.rw1) can have a VLUN associated with it.

The command will remember the VLUN, remove the old snapshot, create a new snapshot, and recreate the VLUN with the new snapshot. However, the read-only parent cannot have any VLUNs.

If the read-only parent (test.ro1) has any associated VLUNs, this command will fail.

After the snapshot is replaced, testuser1 must remount the filesystem on the host.

172 Using mySnapshot

18 Performance Tuning

Analyzing and Tuning a System

The tunesys command analyzes your entire system and automatically corrects space usage imbalances in the system. Virtual volume and physical disk capacity are analyzed and rebalanced for optimal performance. Access to the virtual volumes is not interrupted during the system tuning operations.

Analyze and tune the system by issuing the tunesys -nodepct <percentage> -chunkpct

<percentage> -diskpct <percentage> command, where:

•

-nodepct <percentage> controls internode tuning. Virtual volumes are analyzed for balance between nodes. If any node has an imbalance of more than <percentage>, the virtual volume will be rebalanced. The threshold <percentage> must be between 1 and

100. The default value is 3.

•

-chunkpct <percentage> controls intranode tuning in conjunction with the -diskpct option. Specifies that if a physical disk contains -diskpct <percentage> more chunklets than average for the same device type, chunklets from the overused physical disk can be moved to under used physical disks associated with the same node. The threshold -chunkpct

<percentage> must be between 1 and 100. The default value is 5. This option cannot be used with the -cpg option.

•

-diskpct <percentage> controls intranode tuning in conjunction with the -chunkpct option. Specifies the percentage of disks identified by the -chunkpct <percentage> option required to initiate moving chunklets from overused physical disks to under used physical disks on a node. The threshold -diskpct <percentage> must be between 1 and 100.

The default value is 10. This option cannot be used with the -cpg option.

Other options for controlling the tunesys command:

•

-cpg <cpg_name|pattern> limits the tunesys operations to the specified CPGs. The specified CPGs must all be in the same domain as the CLI user. The -cpg option cannot be used with the -nodepct <percentage> and -chunkpct <percentage> options.

Intranode tuning does not take place if the -cpg option is specified.

•

-maxchunk <number> indicates the maximum number of chunklets that can be moved from any PD in a single operation. The <number> must be between 1 and 8. The default value is

•

-tunenodech limits chunklet level rebalancing to the intranode level.

•

-dr indicates the command is a dry run and no tuning operations are performed. Use the showtask command to view a summary of the analysis and rebalancing operations.

•

-maxtasks <number> specifies the maximum number of individual tuning tasks the tunesys command can run simultaneously. The <number> must be between 1 and 8. The default value is 2.

•

-waittask specifies that all tasks created by the tunesys command will complete before returning.

•

-f specifies the system will not ask for confirmation before initiating the tunesys command.

You can schedule, monitor, and manage the tunesys command operations as a system task. For information about system tasks, see

“Managing Tasks” (page 126) .

For more information about when to use the Dynamic Optimization feature and the tunesys command, see the HP 3PAR StoreServ Storage Concepts Guide.

Analyzing and Tuning a System 173

NOTE: Running the tunesys command does not eliminate the need to run the tunepd command.

The tunesys command performs space based balancing. The tunepd command performs service time and I/O based balancing.

The tunesys command verifies that LDs associated with a CPG have the same characteristics as the CPG. If the LD characteristics do not match the CPG, the LD is modifed to match the CPG characteristics.

Displaying Virtual Volume Space Distribution

The showvvcpg command displays how virtual volume space is distributed among CPGs.

Display virtual volume space distribution by issuing the showvvcpg -domain

<domain_name|pattern> <vv_name|pattern|vv_set> command, where:

•

-domain <domain_name|pattern> designates only virtual volumes that are in domains with names matching one or more of the specified domain names or patterns is displayed.

Only virtual volumes within domains that the user is a member of can be listed. Multiple domain names or patterns can be repeated using a comma-separated list.

•

<vv_name|pattern|set:vv_set_name> indicates which virtual volumes, patterns, or virtual volume sets are displayed. The virtual volume set specifier must start with set: and followed by a virtual volume set name or pattern.

For more information about the showvvcpg command, see the HP 3PAR StoreServ Storage

Command Line Interface Reference.

Tuning and Modifying Virtual Volumes

Use the tunevv command to improve the performance of a system by modifying the virtual volumes to use all available hardware resources. You can also change the parameters, RAID levels, and set sizes for virtual volumes. Modifying virtual volumes does not interrupt access to the virtual volumes.

A good time to use the tunevv command is after changing the hardware configuration of your system. When a system is upgraded by adding nodes, cages, or physical disks, the initial volume and LD layouts may no longer be optimal for the new system configuration. Tuning your system enables you to optimize the layout of volumes for the new system configuration.

You can schedule, monitor, and manage the tunevv command operations as a system task. For information about system tasks, see

“Managing Tasks” (page 126) .

For more information about when to use the Dynamic Optimization feature and the tunevv command, see the HP 3PAR StoreServ Storage Concepts Guide.

Changing Virtual Volume Layouts

Use the tunevv command to change the virtual volume’s parameters, RAID levels, and set sizes by associating the virtual volume with a new CPG.

To change the layout of volumes following a hardware upgrade, perform the following:

Procedure 1

Create a new CPG. See

“Creating a Common Provisioning Group” (page 80)

for instructions.

Change the layout of the volume by issuing the tunevv usr_cpg <CPG_name> <VV_name> command, where:

• usr_cpg <CPG_name> is the name of the CPG created previously in

Step 1 , indicating

the user space of the new CPG will be used.

•

<VV_name> is the volume you are modifying.

174 Performance Tuning

Thinly-Provisioned Virtual Volumes

By default, TPVVs and their underlying CPGs dedicate space from all available resources as they grow, both from preexisting and new drive capacity resources. This natural expansion capability of TPVVs reduces the need for changing the layout of TPVVs after adding disks.

To change the layout of TPVVs following a hardware upgrade, perform the following:

Create a new CPG. See

“Creating a Common Provisioning Group” (page 80)

for instructions.

Tune the user space of the volume by issuing the tunevv usr_cpg <CPG_name>

<volume_name> command, where:

• usr_cpg <CPG_name> is the name of the CPG created in

Step 1

, indicating the user space of the new CPG will be used.

•

<volume_name> is the TPVV you are modifying.

Tune the snapshot space of the volume by issuing the tunevv snp_cpg <CPG_name>

<volume_name> command, where:

• snp_cpg <CPG_name> indicates the CPG to where the snapshot space is moved.

•

<volume_name> is the TPVV you are modifying.

Fully-Provisioned Virtual Volumes

To change the layout of FPVVs following a hardware upgrade, perform the following:

Create a new CPG. See

“Creating a Common Provisioning Group” (page 80)

for instructions.

Tune the user space of the volume by issuing the tunevv usr_cpg <CPG_name>

<volume_name> command, where:

• usr_cpg <CPG_name> is the name of the CPG created previously in

Step 1 , indicating

the user space of the new CPG will be used.

•

<volume_name> is the fully-provisioned virtual volume you are modifying.

Tune the snapshot space of the volume by issuing the tunevv snp_cpg <CPG_name>

<volume_name> command:

• snp_cpg <CPG_name> indicates the CPG to where the snapshot space is moved.

•

<volume_name> is the fully-provisioned virtual volume you are modifying.

Changing Virtual Volume RAID Levels

Thinly-Provisioned Virtual Volumes

To change the RAID type of a TPVV, perform the following:

Create a new CPG with the RAID type to which you wish to change the volume. See

“Creating a Common Provisioning Group” (page 80)

for instructions.

Change the TPVV’s RAID type by issuing the tunevv usr_cpg <CPG_name> <TPVV_name> command, where:

• usr_cpg <CPG_name> is the name of the CPG created previously in

Step 1

•

<TPVV_name> is the TPVV whose RAID type you are changing.

Fully-Provisioned Virtual Volumes

To change the RAID type of a fully-provisioned virtual volume, perform the following:

Create a new CPG with the RAID type to which you wish to change the volume. See

“Creating a Common Provisioning Group” (page 80)

for instructions.

Tuning and Modifying Virtual Volumes 175

Tune the user space of the volume by issuing the tunevv usr_cpg <CPG_name>

<volume_name> command, where:

• usr_cpg <CPG_name> is the name of the CPG created previously in

Step 1 , indicating

the user space of the new CPG will be used.

•

<volume_name> is the fully-provisioned virtual volume you are modifying.

Tune the snapshot space of the volume by issuing the tunevv snp_cpg <CPG_name>

<volume_name> command:

• snp_cpg <CPG_name> indicates the CPG to where the snapshot space is moved.

•

<volume_name> is the fully-provisioned virtual volume you are modifying.

Changing Virtual Volume Fault-Tolerance Levels

Thinly-Provisioned Virtual Volumes

To change the volume fault-tolerance level of a TPVV, perform the following:

Create a new CPG with the desired fault-tolerance level and RAID type. See

“Creating a

Common Provisioning Group” (page 80)

for instructions.

Change the TPVV’s fault-tolerance level by issuing the tunevv usr_cpg <CPG_name>

<TPVV_name> command, where:

• usr_cpg <CPG_name> is the name of the CPG created previously in

Step 1

•

<TPVV_name> is the TPVV you are modifying.

Fully-Provisioned Virtual Volumes

To change the volume fault-tolerance level of a fully-provisioned virtual volume, perform the following:

Create a new CPG with the desired fault-tolerance level and RAID type. See “Creating a

Common Provisioning Group” (page 80)

for instructions.

Change the fully-provisioned virtual volume’s fault-tolerance level by issuing the tunevv usr_cpg <CPG_name> <volume_name> command, where:

• usr_cpg <CPG_name> is the name of the CPG created previously in

Step 1

•

<volume_name> is the fully-provisioned virtual volume you are modifying.

Tune the snapshot space of the volume by issuing the tunevv snp_cpg <CPG_name>

<volume_name> command:

• snp_cpg <CPG_name> indicates the CPG to where the snapshot space is moved.

•

<volume_name> is the fully-provisioned virtual volume you are modifying.

Changing Virtual Volume Parameters

Thinly-Provisioned Virtual Volumes

To change the parameters of a TPVV, perform the following:

Create a new CPG with the parameters you wish to apply to the volume. See

“Creating a

Common Provisioning Group” (page 80)

for instructions.

Issue the tunevv usr_cpg <CPG_name> <TPVV_name> command, where:

• usr_cpg <CPG_name> is the name of the CPG created previously in

Step 1

•

<TPVV_name> is the TPVV you are modifying.

Fully-Provisioned Virtual Volumes

To change the parameters of a fully-provisioned virtual volume, perform the following:

176 Performance Tuning

Create a new CPG with the parameters you wish to apply to the volume. See

“Creating a

Common Provisioning Group” (page 80)

for instructions.

Issue the tunevv usr_cpg <CPG_name> <volume_name> command, where:

• usr_cpg <CPG_name> is the name of the CPG created previously in

Step 1

•

<volume_name> is the fully-provisioned virtual volume you are modifying.

Tune the snapshot space of the volume by issuing the tunevv snp_cpg <CPG_name>

<volume_name> command:

• snp_cpg <CPG_name> indicates the CPG to where the snapshot space is moved.

•

<volume_name> is the fully-provisioned virtual volume you are modifying.

Troubleshooting Modifying Virtual Volumes

When performing a tunevv task, errors can occur that can interrupt the task. Depending on the cause of interruption, you can either rollback or restart a tunevv task.

You can schedule, monitor, and manage the tunevv command operations as a system task. For information about system tasks, see

“Managing Tasks” (page 126) .

CAUTION: Rollback and restart operations should not be performed on TPVVs.

Rolling Back a Volume Modification Task

Rolling back a tunevv task restores a volume to its state prior to the initiation of the task. Essentially, issuing a rollback command performs an undo of the operation. You may choose to roll back a tunevv task if the operation was interrupted because of:

•

Lack of space.

•

User-initiated cancellation of a task.

To perform a rollback operation, perform the following:

Issue the canceltask <task_ID> command, where <task_ID> is the ID of the tunevv task you wish to cancel. For more information about tasks and viewing tasks, see

“Managing

Tasks” (page 126)

Issue the tunevv rollback <VV_name> command.

Restarting a Volume Modification Task

Restarting a tunevv task restarts a task that was previously interrupted. You may choose to restart a tunevv task if the operation was interrupted because of:

•

User-initiated cancellation of a task.

•

Component failure.

To restart a tunevv task, issue the tunevv restart <VV_name> command.

Tuning Physical Disks

HP 3PAR System Tuner Software is an optional feature that improves performance by identifying over-used physical disks, and performing load balancing on those disks without interrupting access.

Use the tunepd command to perform tuning tasks on physical disks. You must purchase the HP

3PAR System Tuner Software license to use the tunepd command.

Troubleshooting Modifying Virtual Volumes 177

If the performance of one or more physical disks degrades, the throughput of the LDs is reduced and the entire system performance may decline. There are two general reasons why a physical disk may have degraded performance:

•

The physical disk has reached its maximum throughput due to an unbalanced load. A disk in this state typically has unusually high average service times when compared to other disks.

•

The physical disk is a bad disk. A bad disk typically has unusually high maximum service times when compared to other disks.

The tunepd command allows you to:

•

Perform physical disk performance tuning on an entire system or on a specified subset of disks.

•

Set performance thresholds for physical disk tuning.

•

Identify and relocate under-performing chunklets.

In the following example, physical disks with average service times exceeding 50 milliseconds are identified and their chunklets are automatically relocated to rebalance the load on the physical disks.

To tune physical disks, issue the tunepd -vvlayout -chstat -movech auto avgsvct

50 command, where:

•

<vvlayout> specifies that the layout of the virtual volume is displayed.

•

<chstat> specifies that chunklet statistics are displayed.

•

<movech> specifies that if any disks with unbalanced loads are detected, the chunklets are moved from those disks for load balancing

•

<auto> specifies that the system automatically chooses source and destination chunklets.

•

<avgsvct> specifies the average service time threshold in milliseconds.

For more information about viewing system performance statistics, see

“Viewing Statistics and

Histograms” (page 121) . For more information about how the system manages space usage, see

the HP 3PAR StoreServ Storage Concepts Guide.

NOTE: Running the tunepd command does not eliminate the need to run the tunesys command.

The tunesys command performs space based balancing. The tunepd command performs service time and I/O based balancing.

Compacting Logical Disks

Reclaim unused LD space with the compactcpg command. When multiple identical virtual volumes are created as a result of a single volume creation operation, the underlying LDs that support those volumes are shared by the volume group. If several of the members of that volume group are later deleted, the underlying LDs may become less efficient in the usage of space. One or more LDs shared by the volume group may have only a small portion of their regions mapped to existing virtual volumes. However, their unused regions are not available to the system for use in creating new LDs. Compacting the LD regions mapped to these volumes may recover and free LD space.

For more information about how the system manages space usage, see the HP 3PAR StoreServ

Storage Concepts Guide.

You can compact LDs for a group of volumes that share LDs with the compactld command.

Existing regions on the fragmented LDs are migrated to new, fully use LDs and the older ones are deleted so that unused space can be returned to the system’s free chunklet pool.

To reclaim unused LD space from the group of virtual volumes, issue thecompactld <LD_name> or compactld -pat <pattern> command, where:

•

<LD_name> is the name of the LD you wish to compact.

•

<pattern> displays all LDs that match the pattern.

178 Performance Tuning

See the HP 3PAR Command Line Interface Reference and the HP 3PAR CLI Help for detailed information about this command.

Compacting Common Provisioning Groups

Reclaim unused CPG space with the compactld command. CPGs provide a shared pool of LD capacity for use by all virtual volumes that draw space from that pool. If volumes that draw from a CPG are deleted, or if copy space for these volumes grows and then shrinks, the underlying LDs in the CPG pool can become less efficient in space usage. Compacting a CPG allows you to reclaim space from a CPG that has become less efficient in space usage from creating, deleting, and relocating volumes. Compacting consolidates LD space in CPGs into as few LDs as possible.

• compactcpg <CPG_name> or compactcpg <pattern>

◦

<CPG_name> is the name of the CPG you wish to compact.

◦

<pattern> displays all CPGs that match the pattern.

See the HP 3PAR Command Line Interface Reference and the HP 3PAR CLI Help for detailed information about this command.

For more information about how the system manages space usage, see the HP 3PAR StoreServ

Storage Concepts Guide.

Compacting Common Provisioning Groups 179

19 Support and Other Resources

Contacting HP

For worldwide technical support information, see the HP support website: http://www.hp.com/support

Before contacting HP, collect the following information:

•

Product model names and numbers

•

Technical support registration number (if applicable)

•

Product serial numbers

•

Error messages

•

Operating system type and revision level

•

Detailed questions

Specify the type of support you are requesting:

HP 3PAR storage system

HP 3PAR StoreServ 7200, 7400, and 7450 Storage systems

HP 3PAR StoreServ 10000 Storage systems

HP 3PAR T-Class storage systems

HP 3PAR F-Class storage systems

Support request

StoreServ 7000 Storage

3PAR or 3PAR Storage

HP 3PAR documentation

For information about:

Supported hardware and software platforms

Locating HP 3PAR documents

See:

The Single Point of Connectivity Knowledge for HP

Storage Products (SPOCK) website: http://www.hp.com/storage/spock

The HP 3PAR StoreServ Storage site: http://www.hp.com/go/3par

To access HP 3PAR documents, click the Support link for your product.

Storage concepts and terminology

HP 3PAR storage system software

HP 3PAR StoreServ Storage Concepts Guide

Using the HP 3PAR Management Console (GUI) to configure and administer HP 3PAR storage systems

HP 3PAR Management Console User's Guide

Using the HP 3PAR CLI to configure and administer storage systems

HP 3PAR Command Line Interface Administrator’s

Manual

CLI commands

Analyzing system performance

HP 3PAR Command Line Interface Reference

HP 3PAR System Reporter Software User's Guide

Installing and maintaining the Host Explorer agent in order to manage host configuration and connectivity information

HP 3PAR Host Explorer User’s Guide

Creating applications compliant with the Common Information

Model (CIM) to manage HP 3PAR storage systems

HP 3PAR CIM API Programming Reference

180 Support and Other Resources

For information about: See:

Migrating data from one HP 3PAR storage system to another

HP 3PAR-to-3PAR Storage Peer Motion Guide

Configuring the Secure Service Custodian server in order to monitor and control HP 3PAR storage systems

Using the CLI to configure and manage HP 3PAR Remote

Copy

Updating HP 3PAR operating systems

Identifying storage system components, troubleshooting information, and detailed alert information

Installing, configuring, and maintaining the HP 3PAR Policy

Server

HP 3PAR Secure Service Custodian Configuration Utility

Reference

HP 3PAR Remote Copy Software User’s Guide

HP 3PAR Upgrade Pre-Planning Guide

HP 3PAR F-Class, T-Class, and StoreServ 10000 Storage

Troubleshooting Guide

HP 3PAR Policy Server Installation and Setup Guide

HP 3PAR Policy Server Administration Guide

HP 3PAR documentation 181

For information about: See:

Planning for HP 3PAR storage system setup

Hardware specifications, installation considerations, power requirements, networking options, and cabling information for HP 3PAR storage systems

HP 3PAR 7200, 7400, and 7450 storage systems

HP 3PAR 10000 storage systems

HP 3PAR StoreServ 7000 Storage Site Planning Manual

HP 3PAR StoreServ 7450 Storage Site Planning Manual

HP 3PAR StoreServ 10000 Storage Physical Planning

Manual

HP 3PAR StoreServ 10000 Storage Third-Party Rack

Physical Planning Manual

Installing and maintaining HP 3PAR 7200, 7400, and 7450 storage systems

Installing 7200, 7400, and 7450 storage systems and initializing the Service Processor

HP 3PAR StoreServ 7000 Storage Installation Guide

HP 3PAR StoreServ 7450 Storage Installation Guide

HP 3PAR StoreServ 7000 Storage SmartStart Software

User’s Guide

Maintaining, servicing, and upgrading 7200, 7400, and

7450 storage systems

Troubleshooting 7200, 7400, and 7450 storage systems

HP 3PAR StoreServ 7000 Storage Service Guide

HP 3PAR StoreServ 7450 Storage Service Guide

HP 3PAR StoreServ 7000 Storage Troubleshooting Guide

HP 3PAR StoreServ 7450 Storage Troubleshooting Guide

Maintaining the Service Processor

HP 3PAR Service Processor Software User Guide

HP 3PAR Service Processor Onsite Customer Care

(SPOCC) User's Guide

HP 3PAR host application solutions

Backing up Oracle databases and using backups for disaster recovery

HP 3PAR Recovery Manager Software for Oracle User's

Guide

Backing up Exchange databases and using backups for disaster recovery

HP 3PAR Recovery Manager Software for Microsoft

Exchange 2007 and 2010 User's Guide

Backing up SQL databases and using backups for disaster recovery

Backing up VMware databases and using backups for disaster recovery

HP 3PAR Recovery Manager Software for Microsoft SQL

Server User’s Guide

HP 3PAR Management Plug-in and Recovery Manager

Software for VMware vSphere User's Guide

Installing and using the HP 3PAR VSS (Volume Shadow Copy

Service) Provider software for Microsoft Windows

HP 3PAR VSS Provider Software for Microsoft Windows

User's Guide

Best practices for setting up the Storage Replication Adapter for VMware vCenter

HP 3PAR Storage Replication Adapter for VMware vCenter Site Recovery Manager Implementation Guide

Troubleshooting the Storage Replication Adapter for VMware vCenter Site Recovery Manager

HP 3PAR Storage Replication Adapter for VMware vCenter Site Recovery Manager Troubleshooting Guide

Installing and using vSphere Storage APIs for Array

Integration (VAAI) plug-in software for VMware vSphere

HP 3PAR VAAI Plug-in Software for VMware vSphere

User's Guide

182 Support and Other Resources

Typographic conventions

Table 17 Document conventions

Convention

Bold text

Monospace text

Element

•

Keys that you press

•

Text you typed into a GUI element, such as a text box

•

GUI elements that you click or select, such as menu items, buttons, and so on

•

File and directory names

•

System output

•

Code

•

Commands, their arguments, and argument values

•

Code variables

•

Command variables

Bold monospace text

•

Commands you enter into a command line interface

•

System output emphasized for scannability

WARNING!

Indicates that failure to follow directions could result in bodily harm or death, or in irreversible damage to data or to the operating system.

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

NOTE: Provides additional information.

Required

Indicates that a procedure must be followed as directed in order to achieve a functional and supported implementation based on testing at HP.

HP 3PAR branding information

•

The server previously referred to as the "InServ" is now referred to as the "HP 3PAR StoreServ

Storage system."

•

The operating system previously referred to as the "InForm OS" is now referred to as the "HP

3PAR OS."

•

The user interface previously referred to as the "InForm Management Console (IMC)" is now referred to as the "HP 3PAR Management Console."

•

All products previously referred to as “3PAR” products are now referred to as "HP 3PAR" products.

Typographic conventions 183

20 Documentation feedback

HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback

( [email protected]

). Include the document title and part number, version number, or the URL when submitting your feedback.

184 Documentation feedback

A Mapping Roles and Rights

In this appendix

•

“3PAR AO Role” (page 185)

•

“3PAR RM Role” (page 185)

•

“Basic Edit Role” (page 186)

•

“Browse Role” (page 188)

•

“Create Role” (page 188)

•

“Edit Role” (page 189)

•

“Service Role” (page 191)

•

“Super Role” (page 192)

3PAR AO Role

Table 18 3PAR AO Rights

Right cpg_compact password_checkown password_setown reg_move

Description of Right

Consolidate space in a CPG.

Check a user's own password.

Set a user's own password.

Move virtual volume regions between LDs.

3PAR RM Role

Table 19 3PAR RM Role

Right groupsv_create host_set ld_remove password_checkown password_setown rcopy_start rcopy_stop rcopy_sync rcopygroup_create rcopygroup_set rcopygroup_start rcopygroup_stop rcopytarget_admit rcopytarget_set sched_create sched_setown

Description of Right

Create a virtual volume group.

Set host properties.

Remove an LD.

Check a user's own password.

Set a user's own password.

Start the remote copy service.

Stop the remote copy service.

Synchronize remote copy groups.

Create a remote copy group.

Set remote copy group properties.

Start remote copy group.

Stop a remote copy group.

Add a target to a remote copy volume.

Set remote copy target properties.

Create a schedule for tasks.

Set a user's own scheduled task properties.

3PAR AO Role 185

Basic Edit Role

Table 20 Edit Rights

Right alert_set authparam_set cpg_compact cpg_create domain_create domain_moveto domainset_create domainset_set groupsv_create groupvvcopy_create health_check host_create host_set hostset_create hostset_set ld_remove password_checkown

Right sshkey_remove sshkey_set sv_create sv_promote sv_remove sv_set task_start user_setown vlun_create vlun_remove vv_create vvcopy_remove vvcopy_set vvset_create vvset_set

Table 19 3PAR RM Role (continued)

Description of Right

Remove users public SSH keys.

Set the public SSH key for a user.

Create a virtual copy volume.

Promote a virtual copy volume.

Remove virtual copy of a volume.

Set properties of a virtual copy of a volume.

Run commands in the background.

Set a user's own properties.

Export a virtual volume as a SCSI LUN.

Remove a VLUN.

Create a Virtual Volume.

Remove physical copy of a volume.

Set properties of a physical copy of a volume.

Create a virtual volume set.

Set virtual volume set properties.

Description of Right

Set alert properties.

Set LDAP authentication properties.

Consolidate space in a CPG.

Create CPG.

Create a domain.

Move objects in or out of a domain.

Create a domain set.

Set domain set properties.

Create a virtual volume group.

Create a physical copy volume group.

Check the current health of the system.

Create a host.

Set host properties.

Create paths to a system host set.

Set host set properties.

Remove an LD.

Check a user's own password.

186 Mapping Roles and Rights

Table 20 Edit Rights (continued)

Right password_setown rcopy_start rcopy_stop rcopy_sync rcopygroup_create rcopygroup_remove rcopygroup_set rcopygroup_start rcopygroup_stop rcopylink_admit rcopylink_dismiss rcopytarget_admit rcopytarget_create rcopytarget_dismiss rcopytarget_remove rcopytarget_set rcopyvv_admit rcopyvv_dismiss sched_create sched_setown snapspace_update sshkey_set sv_create sv_promote sv_remove sv_set user_create user_setown vlun_create vv_create vv_grow vv_tune vvcopy_create vvcopy_promote vvcopy_remove vvcopy_set

Description of Right

Set a user's own password.

Start the remote copy service.

Stop the remote copy service.

Synchronize remote copy groups.

Create a remote copy group.

Remove a remote copy group.

Set remote copy group properties.

Start remote copy group.

Stop a remote copy group.

Add remote copy links.

Dismiss remote copy links.

Add a target to a remote copy volume.

Create a remote copy target.

Dismiss a remote copy target from a group.

Remove a remote copy target.

Set remote copy target properties.

Add a volume to a remote copy volume group.

Dismiss a virtual volume from a remote copy group.

Create a schedule for tasks.

Set a user's own scheduled task properties.

Update snapshot space accounting information.

Set the public SSH key for a user.

Create a virtual copy volume.

Promote a virtual copy volume.

Remove virtual copy of a volume.

Set properties of a virtual copy of a volume.

Create a user.

Set a user's own properties.

Export a virtual volume as a SCSI LUN.

Create a Virtual Volume.

Grow a virtual volume.

Tune a virtual volume.

Create physical copy volume.

Promote a physical volume back to its base volume.

Remove physical copy of a volume.

Set properties of a physical copy of a volume.

Basic Edit Role 187

Table 20 Edit Rights (continued)

Right vvset_create vvset_set

Description of Right

Create a virtual volume set.

Set virtual volume set properties.

Browse Role

Table 21 Browse Rights

Right password_checkown password_setown sshkey_remove sshkey_set user_setown vv_update

Description of Right

Check a user's own password.

Set a user's own password.

Remove users public SSH keys.

Set the public SSH key for a user.

Set a user's own properties.

Remove old virtual copy and create a new virtual copy of a volume.

Create Role

Table 22 Create Rights

Right cpg_create domainset_annotate domainset_create groupsv_create groupvvcopy_create health_check host_create hostset_annotate hostset_create password_checkown password_setown sched_create sched_setown sv_create vlun_create vv_create vvcopy_create vvset_annotate vvset_create

Description of Right

Create Common Provision Group.

Annotate the comment of a domain set.

Create a domain set.

Create a virtual volume group.

Create a physical copy volume group.

Check the current health of the system.

Create a host.

Annotate the comment of a host set.

Create paths to a system host set.

Check a user's own password.

Set a user's own password.

Create a schedule for tasks.

Set a user's own scheduled task properties.

Create a virtual copy volume.

Export a virtual volume as a SCSI LUN.

Create a Virtual Volume.

Create physical copy volume.

Annotate the comment of a virtual volume set.

Create a virtual volume set.

188 Mapping Roles and Rights

Edit Role

Table 23 Edit Rights

Right aocfg_start ch_move ch_movetospare cpg_compact cpg_create cpg_set domain_moveto domainset_annotate domainset_create domainset_set groupsv_create groupvvcopy_create host_create host_remove host_set hostset_annotate hostset_create hostset_set ld_compact ld_create ld_remove password_checkown password_setown pd_movetospare rclink_check rcopy_start rcopy_stop rcopy_sync rcopygroup_create rcopygroup_remove rcopygroup_set rcopygroup_start rcopygroup_stop rcopylink_admit rcopylink_dismiss

Description of Right

Start execution of an Adaptive Optimization configuration.

Move chunklets from one physical disk to another.

Move chunklets from a physical disk to spare space.

Consolidate space in a CPG.

Create CPG.

Set CPG properties.

Move objects in or out of a domain.

Annotate the comment of a domain set.

Create a domain set.

Set domain set properties.

Create a virtual volume group.

Create a physical copy volume group.

Create a host.

Remove a host.

Set host properties.

Annotate the comment of a host set.

Create paths to a system host set.

Set host set properties.

Consolidate space in an LD.

Create an LD.

Remove an LD.

Check a user's own password.

Set a user's own password.

Move used chunklets from a physical disk to spare space.

Remote copy link validity checks.

Start the remote copy service.

Stop the remote copy service.

Synchronize remote copy groups.

Create a remote copy group.

Remove a remote copy group.

Set remote copy group properties.

Start remote copy group.

Stop a remote copy group.

Add remote copy links.

Dismiss remote copy links.

Edit Role 189

Table 23 Edit Rights (continued)

Right rcopytarget_admit rcopytarget_create rcopytarget_dismiss rcopytarget_remove rcopytarget_set rcopyvv_admit rcopyvv_dismiss reg_move snapspace_update sshkey_remove sshkey_set sv_create sv_promote sv_remove sv_set task_cancel task_remove task_set task_start user_setown useracl_set vlun_create vlun_remove vv_create vv_grow vv_import vv_remove vv_set vv_tune vv_update vvcopy_create vvcopy_promote vvcopy_remove vvcopy_set vvset_annotate

Description of Right

Add a target to a remote copy volume.

Create a remote copy target.

Dismiss a remote copy target from a group.

Remove a remote copy target.

Set remote copy target properties.

Add a volume to a remote copy volume group.

Dismiss a virtual volume from a remote copy group.

Move virtual volume regions between LDs.

Update snapshot space accounting information.

Remove users public SSH keys.

Set the public SSH key for a user.

Create a virtual copy volume.

Promote a virtual copy volume.

Remove virtual copy of a volume.

Set properties of a virtual copy of a volume.

Cancel a task.

Remove a task.

Edit tasks.

Run commands in the background.

Set a user's own properties.

Set user Access Control List properties.

Export a virtual volume as a SCSI LUN.

Remove a VLUN.

Create a Virtual Volume.

Grow a virtual volume.

Import a remote virtual volume to local storage.

Remove a base Virtual Volume.

Set virtual volume properties.

Tune a virtual volume.

Remove old virtual copy and create a new virtual copy of a volume.

Create physical copy volume.

Promote a physical volume back to its base volume.

Remove physical copy of a volume.

Set properties of a physical copy of a volume.

Annotate the comment of a virtual volume set.

190 Mapping Roles and Rights

Table 23 Edit Rights (continued)

Right vvset_create vvset_set

Description of Right

Create a virtual volume set.

Set virtual volume set properties.

Service Role

Table 24 Service Rights ld_remove ld_start mag_control mag_service node_locate node_service node_set node_shutdown password_checkown password_setown pd_admit pd_control pd_dismiss pd_movereloc pd_movetospare

Right alert_remove alert_set battery_set cage_locate cage_set cage_upgrade ch_move ch_movetospare cim_set cim_start cpg_set date_set health_check host_service ld_create

Description of Right

Remove alerts.

Set alert properties.

Set battery properties.

Locate a drive cage.

Set cage properties.

Upgrade cage firmware.

Move chunklets from one physical disk to another.

Move chunklets from a physical disk to spare space.

Set CIM server properties.

Starts the CIM server.

Set Common Provision Group properties.

Set system date and time properties.

Check the current health of the system.

Service a host.

Create an LD.

Remove an LD.

Start an LD.

Take magazines or disks on or off a loop.

Service a magazine or physical disk.

Locate a controller node by blinking its LEDs.

Service a controller node.

Set controller node properties.

Shutdown a controller node.

Check a user's own password.

Set a user's own password.

Admit a physical disk to the system.

Spin up or spin down a physical disk.

Dismiss a physical disk from the system.

Move relocated chunklets from one physical disk to another.

Move used chunklets from a physical disk to spare space.

Service Role 191

Right pd_set pd_upgrade port_check port_control sched_create sched_setany sched_setown spare_create sshkey_remove sshkey_set sys_locate sys_set sys_shutdown task_start vv_check vv_start wsapi_start wsapi_stop

Table 24 Service Rights (continued)

Description of Right

Set physical disk properties.

Update physical disk firmware.

Perform diagnostic tests on ports.

Control and configure ports.

Create a schedule for tasks.

Set any user scheduled task properties.

Set a user's own scheduled task properties.

Create spare chunklet.

Remove users public SSH keys.

Set the public SSH key for a user.

Locate a system by blinking its LEDs.

Set System Properties.

Shutdown the system.

Run commands in the background.

Virtual volume validity checks.

Start a virtual volume.

Start the Web Services API server.

Stop the Web Services API server.

Super Role

Table 25 Super Rights

Right alert_remove alert_set aocfg_start authparam_set battery_set cage_locate cage_set cage_upgrade ch_move ch_movetospare cim_set cim_start cpg_compact cpg_create

Description of Right

Remove alerts.

Set alert properties.

Start execution of an Adaptive Optimization configuration.

Set LDAP authentication properties.

Set battery properties.

Locate a drive cage.

Set cage properties.

Upgrade cage firmware.

Move chunklets from one physical disk to another.

Move chunklets from a physical disk to spare space.

Set CIM server properties.

Starts the CIM server.

Consolidate space in a CPG.

Create CPG.

192 Mapping Roles and Rights

Table 25 Super Rights (continued)

Right cpg_set date_set domain_create domain_moveto domain_remove domain_set domainset_annotate domainset_create domainset_set encryption_control encryption_status eventlog_remove groupsv_create groupvvcopy_create health_check host_create host_remove host_service host_set hostset_annotate hostset_create hostset_set ld_compact ld_create ld_remove ld_start mag_control mag_service node_locate node_service node_set node_shutdown password_checkany password_checkown password_setany password_setown

Description of Right

Set CPG properties.

Set system date and time properties.

Create a domain.

Move objects in or out of a domain.

Remove a domain.

Set domain properties.

Annotate the comment of a domain set.

Create a domain set.

Set domain set properties.

Perform encryption operations (enable, back up, restore, rekey).

Check encryption status of the system.

Remove the system event log.

Create a virtual volume group.

Create a physical copy volume group.

Check the current health of the system.

Create a host.

Remove a host.

Service a host.

Set host properties.

Annotate the comment of a host set.

Create paths to a system host set.

Set host set properties.

Consolidate space in an LD.

Create an LD.

Remove an LD.

Start an LD.

Take magazines or disks on or off a loop.

Service a magazine or physical disk.

Locate a controller node by blinking its LEDs.

Service a controller node.

Set controller node properties.

Shutdown a controller node.

Check any user password.

Check a user's own password.

Change any user password.

Set a user's own password.

Super Role 193

Table 25 Super Rights (continued)

Right pd_admit pd_control pd_dismiss pd_movereloc pd_movetospare pd_set pd_upgrade port_check port_control rclink_check rcopy_start rcopy_stop rcopy_sync rcopygroup_create rcopygroup_remove rcopygroup_set rcopygroup_start rcopygroup_stop rcopylink_admit rcopylink_dismiss rcopytarget_admit rcopytarget_create rcopytarget_dismiss rcopytarget_remove rcopytarget_set rcopyvv_admit rcopyvv_dismiss reg_move sched_create sched_remove sched_setany sched_setown snapspace_update snmpmgr_add snmpmgr_remove snmppw_remove

Description of Right

Admit a physical disk to the system.

Spin up or spin down a physical disk.

Dismiss a physical disk from the system.

Move relocated chunklets from one physical disk to another.

Move used chunklets from a physical disk to spare space.

Set physical disk properties.

Update physical disk firmware.

Perform diagnostic tests on ports.

Control and configure ports.

Remote copy link validity checks.

Start the remote copy service.

Stop the remote copy service.

Synchronize remote copy groups.

Create a remote copy group.

Remove a remote copy group.

Set remote copy group properties.

Start remote copy group.

Stop a remote copy group.

Add remote copy links.

Dismiss remote copy links.

Add a target to a remote copy volume.

Create a remote copy target.

Dismiss a remote copy target from a group.

Remove a remote copy target.

Set remote copy target properties.

Add a volume to a remote copy volume group.

Dismiss a virtual volume from a remote copy group.

Move virtual volume regions between LDs.

Create a schedule for tasks.

Remove a schedule for tasks.

Set any user scheduled task properties.

Set a user's own scheduled task properties.

Update snapshot space accounting information.

Add an SNMP manager.

Remove an SNMP manager.

Remove an SNMP community strings.

194 Mapping Roles and Rights

Table 25 Super Rights (continued)

Right snmppw_set spare_create sshkey_remove sshkey_set sv_create sv_promote sv_remove sv_set sys_locate sys_set sys_shutdown task_cancel task_remove task_set task_start template_create template_remove template_set user_create user_remove vv_create vv_grow vv_import vv_remove vv_set vv_start vv_tune vv_update user_setany user_setown useracl_set userconn_remove vlun_create vlun_remove vv_admit vv_check

Description of Right

Set SNMP community strings.

Create spare chunklet.

Remove users public SSH keys.

Set the public SSH key for a user.

Create a virtual copy volume.

Promote a virtual copy volume.

Remove virtual copy of a volume.

Set properties of a virtual copy of a volume.

Locate a system by blinking its LEDs.

Set System Properties.

Shutdown the system.

Cancel a task.

Remove a task.

Edit tasks.

Run commands in the background.

Create a template for a VV, CPG, or LD.

Remove template for a VV, CPG, or LD.

Set template properties.

Create a user.

Remove a user.

Set any user properties.

Set a user's own properties.

Set user Access Control List properties.

Remove user connections.

Export a virtual volume as a SCSI LUN.

Remove a VLUN.

Admit remote virtual volume to the system.

Virtual volume validity checks.

Create a Virtual Volume.

Grow a virtual volume.

Import a remote virtual volume to local storage.

Remove a base Virtual Volume.

Set virtual volume properties.

Start a virtual volume.

Tune a virtual volume.

Remove old virtual copy and create a new virtual copy of a volume.

Super Role 195

Table 25 Super Rights (continued)

Right vvcopy_create vvcopy_promote vvcopy_remove vvcopy_set vvset_annotate vvset_create vvset_set wsapi_start wsapi_stop

Description of Right

Create physical copy volume.

Promote a physical volume back to its base volume.

Remove physical copy of a volume.

Set properties of a physical copy of a volume.

Annotate the comment of a virtual volume set.

Create a virtual volume set.

Set virtual volume set properties.

Start the Web Services API server.

Stop the Web Services API server.

196 Mapping Roles and Rights

B Mapping Rights and CLI Commands

Right alert_remove alert_set aocfg_start authparam_set battery_set cage_locate cage_set cage_upgrade ch_move ch_movetospare cim_set cim_start cpg_compact cpg_create cpg_set date_set domain_create domain_moveto domain_remove domain_set domainset_annotate domainset_create domainset_set encryption_control encryption_status eventlog_remove groupsv_create groupvvcopy_create health_check host_create host_remove host_service

Mapping Rights and CLI Commands

Table 26 Required Rights for CLI Commands

CLI Commands removealert setalert startao setauthparam setbattery locatecage setcage upgradecage movech movechtospare setcim startcim compactcpg createcpg setcpg setdate createdomain movetodomain removedomain setdomain setdomainset createdomainset setdomainset removedomainset controlencryption controlencryption (status subcommand) removeeventlog creategroupsv creategroupvvcopy checkhealth createhost removehost servicehost

Mapping Rights and CLI Commands 197

Right host_set hostset_annotate hostset_create hostset_set ld_compact ld_create ld_remove ld_start mag_control mag_service node_locate node_service node_set node_shutdown password_checkany password_checkown password_setany password_setown pd_admit pd_control pd_dismiss pd_movereloc pd_movetospare pd_set pd_upgrade port_check port_control rclink_check rcopy_start rcopy_stop rcopy_sync rcopygroup_create rcopygroup_remove rcopygroup_set rcopygroup_start rcopygroup_stop

Table 26 Required Rights for CLI Commands (continued)

CLI Commands sethost sethostset createhostset sethostset, removehostset compactld createald createld removeld startld controlmag servicemag locatenode servicenode setnode shutdownnode checkpassword checkpassword setpassword setpassword admitpd controlpd dismisspd moverelocpd movepdtospare setpd upgradepd checkport controliscsiport controlport checkrclink startrcopy stoprcopy syncrcopy creatercopygroup removercopygroup setrcopygroup startrcopygroup stoprcopygroup

198 Mapping Rights and CLI Commands

Right rcopylink_admit rcopylink_dismiss rcopytarget_admit rcopytarget_create rcopytarget_dismiss rcopytarget_remove rcopytarget_set rcopyvv_admit rcopyvv_dismiss reg_move sched_create sched_remove sched_setany sched_setown snapspace_update snmpmgr_add snmpmgr_remove snmppw_remove snmppw_set spare_create sshkey_remove sshkey_set sv_create sv_promote sv_remove sv_set sys_locate sys_set sys_shutdown task_cancel task_remove task_set task_start template_create template_remove template_set

Table 26 Required Rights for CLI Commands (continued)

CLI Commands admitrcopylink dismissrcopytarget admitrcopytarget creatercopytarget dismissrcopytarget removercopytarget setrcopytarget admitrcopyvv dismissrcopyvv movereg createsched removesched setsched setsched updatesnapspace addsnmpmgr removesnmpmgr removesnmppw setsnmppw createspare removesshkey setsshkey createsv promotesv removevv setvv locatesys setsys shutdownsys canceltask removetask settask starttask createtemplate removetemplate settemplate

Mapping Rights and CLI Commands 199

Right user_create user_remove user_setany user_setown useracl_set userconn_remove vlun_create vlun_remove vv_admit vv_check vv_create vv_grow vv_import vv_remove vv_set vv_start vv_tune vv_update vvcopy_create vvcopy_promote vvcopy_remove vvcopy_set vvset_annotate vvset_create vvset_set wsapi_start wsapi_stop

Table 26 Required Rights for CLI Commands (continued)

CLI Commands createuser removeuser setuser setuser setuseracl removeuserconn createvlun removevlun admitvv checkvv createaldvv createavv createtpvv createvv growaldvv growavv growtpvv growvv importvv removevv setvv startvv tunealdvv tunevv tunetpvv updatevv createvvcopy promotevvcopy removevv setvv setvvset createvvset setvvset removevvset startwsapi stopwsapi

200 Mapping Rights and CLI Commands

Index

A

accessing the CLI,

accessing the CLI using SSH,

Active Directory LDAP configuration using simple binding over SSL,

active VLUNs,

adding and replacing template parameters,

103

adding users to domains,

agents passwords, commands for,

168

registering with setsnmpmgr command,

alerts removing,

setting states,

triggered by events,

viewing,

when spare and free chunklets are used up,

107

applying templates,

102

assigning host paths,

C

capacity physical disk,

106

changing a host domain,

CHAP initiator setting up,

CHAP target setting up,

chunklet histograms, viewing,

124

chunklets free, defined,

107

spare viewing to,

108

CLI (command line interface) displaying help for,

user name restrictions,

command referencing stored passwords,

commands global options effect on,

compactcpg command,

connecting to an HP system, requirements,

controlport command,

conventions text symbols,

183

copies, replacing and restoring,

170

copying virtual volumes resynchronizing physical copy status,

CPGs common provisioning groups,

considerations,

growth increment,

removing,

CPU usage statistics, viewing,

122

createaldvv command,

103

createcpg command,

createhost command,

createtemplate command,

102

createvlun command,

createvv command,

createvvcopy command,

creating a host,

creating domain CPGs,

creating domains,

creating templates,

102

creating TPVVs,

creating VLUN templates,

creating VVs in domains,

current domain,

D

data cache memory statistics, viewing,

122

data encryption,

111

default domain removing,

displaying task information,

127

documentation providing feedback on,

184

domain adding users,

changing host,

creating,

creating CPGs,

creating VVs,

current,

current domain,

default,

freeing VV space,

growing VVs,

modifying,

modifying hosts,

modifying VVs,

moving CPGs,

viewing,

domain association removing,

domains,

drives self-encrypting,

111

E

Environment variable referencing stored passwords,

environment variables

TPDFORCE,

TPDPWFILE,

TPDSTARTFILE,

error log,

installation,

events alerts triggered by,

118

201

export rule,

exporting virtual volumes,

F

Fibre Channel adapter ports setting parameters,

creating a host path,

free chunklets, defined,

107

freeing domain VV space,

freeing virtual volume snapshot space,

freespace command,

Full Copy resynchronizing physical copies,

G

generating a key pair,

Global option referencing stored passwords,

Global options in effect until,

with individual commands,

growing domain VVs,

growing virtual volumes,

growth increment considerations,

H

hardware inventory,

109

Help displaying CLI information,

histograms,

124

host creating,

personas,

host paths assigning,

host sees,

HP 3PAR CLI default installation location,

Solaris installation,

Windows installation,

I

I/O statistics,

122

installation requirements,

InstallShield installation troubleshooting,

uninstalling the CLI,

iSCSI creating a host path,

K

key authentication,

L

LDAP connections configuring connection on systems using Domains,

limitations in Tcl shell,

local key manager,

111

log files installation error log,

logging logical disk allocated at set up,

107

logical disk histograms, viewing,

124

LUN,

M

management consoles registered displayed using showsnmpmgr,

168

registering for SNMP,

168

unregistering with removesnmpmgr,

168

managing domain objects,

, 60

matched set,

modifying domain hosts,

modifying domain VVs,

modifying domains,

modifying templates,

103

monitoring system events,

119

moving domain CPGs,

O

online help,

OpenLDAP configuration using simple binding over SSL,

overview,

P

password and user name, providing,

passwords providing,

referencing stored,

storing of,

use of,

persona,

physical copies promoting,

100

resynchronizing,

physical copy,

physical disk histograms, viewing,

124

port histograms, viewing,

125

port presents,

port statistics, viewing,

121

ports service support level, setting,

setting parameters,

promoting, physical copies,

100

promoting, virtual copies,

R

recovering failed RAID sets,

109

registering the management console,

168

registering the manager with the SNMP agent,

167

removecpg command,

removehost command,

removesnmpmgr command,

168

removesnmppw command,

168

removetemplate command,

104

removevlun command,

202 Index

removing a domain,

removing alerts,

118

removing CPGs,

removing domain objects,

removing tasks,

130

removing template parameters,

104

removing templates,

104

removing the default domain,

removing VLUN templates,

replacing and restoring copies,

170

replacing read-only snapshots,

171

replacing snapshots,

170

reserved user names,

resynchronizing physical copies,

rolling back a virtual copy,

S

scripting,

scripting with SSH,

self-encrypting drives,

111

service support level for ports, setting,

setcpg command,

sethost command,

setpassword for storing password,

setsnmpmgr command,

167

setsnmppw command,

168

settemplate command,

103

setting alert states,

118

setting the current domain,

setting the default domain,

showpd command,

106

showport command,

showsnmpmgr command,

showsnmppw command,

showspare command,

showsys command,

showtemplate command,

103

snapshots replacing,

170

SNMP agent,

167

spare chunklets viewing to,

108

SSH,

benefits to using,

statistics types,

121

viewing,

121

statistics, virtual volumes,

122

symbols in text,

183

system capacity determining,

105

system events, tracking,

118

system name

-sys option not set, action when,

-sys option override,

specifying,

Systems using domains

LDAP configuration,

T

task removing,

130

task information, displaying,

127

task management commands,

126

Tcl shell global option limitations,

template parameters adding and replacing,

removing,

template rules,

templates applying,

creating,

modifying,

removing,

viewing parameters,

templates, allowing overrides,

102

templates, and default values,

102

templates, defined values,

102

templates, included properties,

102

templates, rules for using,

102

templates, specified and unspecified values,

102

text symbols,

183

total physical disk capacity determining,

106

total system capacity,

105

TPDSYSNAME (system name) environment variable

-sys option override,

not set, action when,

setting

Oracle Solaris,

Windows,

TPVVs creating,

traps (SNMP displayed alerts) stopping reception with removesnmpmgr,

168

troubleshooting,

U

unexporting virtual volumes,

uninstalling the CLI,

user name and password, providing,

V

vieiwng template parameters,

103

vieiwng VLUN histograms,

125

viewing alerts,

118

viewing chunklet histograms,

124

viewing CPU usage statistics,

122

viewing data cache memory statistics,

122

viewing domains,

viewing logical disk histograms,

124

viewing physical disk histograms,

124

viewing port histograms,

125

viewing port statistics,

121

viewing statistics,

121

viewing virtual volume histograms,

125

viewing virtual volume statistics,

122

203

virtual copy,

virtual volume histograms, viewing,

125

virtual volume statistics,

122

virtual volume statistics, viewing,

122

virtual volumes exporting,

growing,

resynchronizing physical copy,

snapshot space,

unexporting,

VLUN histograms, viewing,

125

VLUN template host sees,

matched set,

port presents,

removing,

types,

204 Index

Key features

High availability and data protection
Scalability and performance
Easy management
Thin provisioning
Automated tiering
SSD support

Frequently asked questions

The HP 3PAR StoreServ 7400 4-node is a high-performance, scalable storage system designed for demanding enterprise environments.

The key features of the HP 3PAR StoreServ 7400 4-node include high availability and data protection, scalability and performance, and easy management.

The benefits of using the HP 3PAR StoreServ 7400 4-node include improved data protection, increased performance, and reduced management costs.