3PAR CIM API Programming Reference for InForm OS 2.3.1
3PAR Inc. 4209 Technology Drive Fremont, CA 94538 U.S.A. Part No. 320-200164 Rev B February 2010
Revision Notice This is the second release of this manual. A complete revision history is provided at the end of this document.
Changes The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in this document or from the use of the information contained herein. 3PAR reserves the right to make changes in the product design without reservation and without notification to its users.
Updates to the Documentation at 3PAR Central Any updates to this document, or to other 3PAR technical documents, can be found by logging on to 3PAR Central’s Document Control System from 3PAR’s Support page at http://www.3PAR.com/support/index.html
3PAR Technical Support and Services Contact your local service provider for technical support and services.
Sales and Ordering Information For sales and ordering information, contact: 3PAR Inc. 4209 Technology Drive Fremont, CA 94538 U.S.A. Telephone: 510-413-5999 Fax: 510-413-5699 E-mail:
[email protected]
Reader Comments and Suggestions Please E-mail your comments and suggestions about this document to
[email protected].
Copyrights © 2010 3PAR Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of 3PAR Inc., 4245 Technology Drive, Fremont, CA 94538. By way of exception to the foregoing, the user may print one copy of electronic material for personal use only.
Trademarks 3PAR, InServ, InForm, InSpire and Serving Information are registered trademarks of 3PAR Inc. Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. All other trademarks and registered trademarks are owned by their respective owners.
Federal Communications Commission Radio Frequency Interference Statement WARNING: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. This device complies with Part 15 of FFC Rules. Operation is subjected to the following two conditions (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user required to correct the interference at his own expense.
InForm OS Version 2.3.1
CIM API Programming Reference
Table of Contents 1 Introduction 1.1 Audience
1.1
1.2 Related Documentation
1.2
1.3 Organization
1.2
1.4 Typographical Conventions
1.3
1.5 Advisories
1.4
2 Concepts 2.1 About SMI-S
2.1
2.2 About the WBEM Initiative
2.2
3 Security 3.1 TCP Ports
3.1
3.2 Authentication
3.2
3.3 Authorization
3.3
4 Configuring and Using the CIM Server 4.1 CLI Command Overview
4.2
4.2 Enabling and Disabling the CIM Server
4.2
4.2.1
Enabling the CIM Server
4.2
4.2.2
Disabling the CIM Server
4.3
4.3 Displaying the CIM Server Status
4.3 Table of Contents
iii
CIM API Programming Reference
InForm OS Version 2.3.1
4.4 Displaying the CIM Server Version
4.4
4.5 Communicating with the CIM Server
4.4
4.5.1
Client Software
4.4
4.5.2
Sending Client Requests
4.6
4.6 CIM Namespaces
4.7
5 3PAR CIM API SMI-S Support 5.1 Standard Compliance
5.2
5.2 SMI-S Functionality
5.2
5.3 Discovery Service
5.3
5.4 Supported Profiles
5.3
5.5 Supported Array Packages
5.3
5.6 Supported Array Subprofiles
5.4
5.6.1
SMI-S Support by Release
5.5
5.6.2
Discovery Service
5.6
5.7 Server Profile
5.6
5.7.1
Server Profile CIM Classes
5.7
5.7.2
Supported Methods
5.7
5.8 Array Profile
5.8
5.8.1
Array Profile CIM Classes
5.8
5.8.2
Supported Methods
5.8
5.9 Block Services Package
iv
Table of Contents
5.9 5.9
5.9.1
Block Services Package CIM Classes
5.9.2
Supported Methods
5.10
5.9.3
StorageSetting
5.12
5.9.4
Creating a DynamicStoragePool (DSP) via SMI-S
5.18
5.9.4.1
Relevant Properties of DynamicStoragePool
5.21
5.9.4.2
Modifiable StorageSetting Properties for DSP
5.23
5.9.4.3
StorageCapabilities of DynamicStoragePool
5.25
5.9.4.4
StoragePoolConfigurationCapabilities of DynamicStoragePool
5.25
InForm OS Version 2.3.1
CIM API Programming Reference
5.9.5
5.9.6
5.9.7
Creating a Volume Through SMI-S
5.26
5.9.5.1
Supported Method For Creating a Storage Volume
5.28
5.9.5.2
Creating Data and Snapshot Space from Two Storage Pools
5.31
5.9.5.3
CreateSetting
5.34
5.9.5.4
Creating a Volume with a Default Setting
5.35
5.9.5.5
Creating a Volume with a Non-Default Setting
5.35
5.9.5.6
Creating a Volume with Disk Pattern Filtering
5.37
5.9.5.7
Summary of Different Types of Volumes That Can Be Created
5.39
5.9.5.8
Modifiable StorageSetting Properties for StorageVolume
5.44
Calculating Capacity for StoragePool and StorageVolume
5.46
5.9.6.1
Primordial Storage Pool
5.46
5.9.6.2
Concrete Storage Pool
5.46
5.9.6.3
Dynamic Storage Pool (CPG)
5.46
5.9.6.4
Legacy Storage Volume
5.47
5.9.6.5
Fully Provisioned Storage Volume
5.50
5.9.6.6
Thinly Provisioned Storage Volume
5.52 5.55
Indications
5.10 Copy Services Subprofile
5.56
5.10.1
Description
5.56
5.10.2
CIM Classes
5.56
5.10.2.1
TPD_AffectedJobElement
5.59
5.10.2.2
TPD_AllocatedFromStoragePool
5.59
5.10.2.3
TPD_AssociatedJobMethodResult
5.59
5.10.2.4
TPD_CapabilitiesOfStorageConfigurationService
5.59
5.10.2.5
TPD_CapabilitiesOfStoragePool
5.59
5.10.2.6
TPD_ConcreteJob
5.59
5.10.2.7
TPD_ConcreteJobInstModification
5.59
5.10.2.8
TPD_DeltaReplicaStoragePool
5.60
5.10.2.9
TPD_ElementSettingData
5.60
5.10.2.10
TPD_HostedStoragePool
5.60
5.10.2.11
TPD_MethodResult
5.60
5.10.2.12
TPD_OwningJobElement
5.60
Table of Contents
v
CIM API Programming Reference
InForm OS Version 2.3.1
5.10.3
5.10.4
5.10.5
5.10.6
5.10.2.13
TPD_ReplicaPoolForStorage
5.60
5.10.2.14
TPD_StorageCapabilities
5.60
5.10.2.15
TPD_StorageConfigurationCapabilities
5.61
5.10.2.16
TPD_StorageConfigurationService
5.61
5.10.2.17 TPD_StorageReplicationCapabilities
5.62
5.10.2.18
TPD_StorageSetting
5.66
5.10.2.19
TPD_StorageSynchronized
5.66
5.10.2.20
TPD_SystemVolume
5.67
5.10.2.21
TPD_DynamicStoragePool
5.67
SA/SD Space As StoragePool 5.10.3.1
StoragePool Instantiation
5.67
5.10.3.2
Associations
5.68
5.10.3.3
Capacity Calculations
5.68
5.10.3.4
Indications
5.71
Physical Copy
Table of Contents
5.72
5.10.4.1
StorageSynchronized
5.72
5.10.4.2
StorageReplicationCapabilities
5.73
5.10.4.3
Job Control Subprofile Indications
5.84
Virtual Copy
5.84
5.10.5.1
StorageSynchronized
5.84
5.10.5.2
StorageReplicationCapabilities
5.85
Job Control
5.91
5.10.6.1
Overview
5.91
5.10.6.2
TPD_ConcreteJob
5.91
5.10.6.3
TPD_OwningJobElement
5.95
5.10.6.4
TPD_AffectedJobElement
5.95
5.10.6.5
TPD_AssociatedJobMethodResult
5.95
5.10.6.6
Indications
5.95
5.11 Location Subprofile
vi
5.67
5.95
5.11.1
Location Subprofile CIM Classes
5.95
5.11.2
Supported Methods
5.96
InForm OS Version 2.3.1
CIM API Programming Reference
5.12 Multiple Computer System Subprofile
5.96
5.12.1
Multiple Computer System Subprofile CIM Classes
5.96
5.12.2
Supported Methods
5.97
5.13 Software Subprofile
5.97
5.13.1
Software Subprofile CIM Classes
5.97
5.13.2
Supported Methods
5.98
5.14 Masking and Mapping Subprofile
5.98 5.98
5.14.1
Masking and Mapping Subprofile CIM Classes
5.14.2
Supported Methods
5.100
5.14.3
SMI-S View and Paths
5.101
5.14.4
ProtocolControllerMaskingCapabilities
5.105
5.14.5
ControllerConfigurationService
5.107
5.14.5.1
ExposePaths (Creating Matched-Set VLUNs)
5.108
5.14.5.2
HidePaths (Removing Matched-Set VLUNs)
5.112
5.14.5.3
ExposeDefaultLUs (Creating Port-Present VLUNs)
5.114
5.14.5.4
HideDefaultLUs (Removing Port-Present VLUNs)
5.116
5.14.5.5
ExposeLUsToStorageHardwareIDCollection (Creating Host-Sees VLUNs) (3PAR proprietary method)
5.118
5.15 HideLUsFromStorageHardwareIDCollection (Removing Host-Sees VLUNs)
5.121
5.15.0.1
StorageHardwareIDManagementService
5.122
5.15.0.2
CreateStorageHardwareID (Creating Host and Path)
5.123
5.15.0.3
DeleteStorageHardwareID (Removing a Path from a Host)
5.124
5.15.0.4
CreateStorageHardwareIDCollection (Creating a Host)
5.125
5.15.0.5
AddStorageHardwareIDsToCollection (Adding a Path to a Host)
5.126
5.15.0.6
StorageHardwareIDCollection.DeleteInstance (Deleting a Host)
5.126
5.15.1
ConcreteDependency
5.126
5.15.2
SAPAvailableForElement
5.126
5.15.3
iSCSISAPAvailableForElement
5.127
5.15.4
SCSIPrococolController
5.127
5.15.5
iSCSIPrococolController
5.127
5.15.6
SCSIPrococolEndpoint
5.127
Table of Contents
vii
CIM API Programming Reference
InForm OS Version 2.3.1
5.15.7
iSCSIPrococolEndpoint
5.128
5.15.8
ControllerForUnit
5.128
5.15.9
iSCSIControllerForUnit
5.129
5.15.10
StorageClientSettingData
5.130
5.15.11
StorageHardwareID
5.130
5.15.12
TPD_StorageHardwareIDCollection
5.130
5.15.13
Supporting classes
5.130
5.15.13.1
AuthorizedPrivilege
5.130
5.15.13.2
AuthorizedSubject
5.131
5.15.13.3
AuthorizedTarget
5.131
5.15.13.4
ConcreteDependency
5.131
5.15.13.5
SystemEndpoint (HostedAccessPoint)
5.131
5.15.13.6
ElementCapabilities
5.131
5.15.13.7
ElementSettingData
5.131
5.15.13.8
MemberOfCollection
5.131
5.15.13.9
ProtocolControllerMaskingCapabilities
5.131
5.16 FC Target Ports Subprofile 5.16.1
FC Target Ports Subprofile CIM Classes
5.132
5.16.2
Supported Methods
5.132
5.17 FC Initiator Ports Subprofile FC Initiator Ports Subprofile CIM Classes
5.133
5.17.2
Supported Methods
5.133 5.133
5.18.1
iSCSI Target Ports Subprofile CIM Classes
5.134
5.18.2
Supported Methods
5.135
5.19 Disk Drive Lite Subprofile
5.135
5.19.1
Disk Drive Lite Subprofile CIM Classes
5.135
5.19.2
Supported Methods
5.136
5.20 Block Server Performance Subprofile 5.20.1
Table of Contents
5.132
5.17.1
5.18 iSCSI Target Ports Subprofile
viii
5.132
Block Server Performance Subprofile CIM Classes
5.137 5.137
InForm OS Version 2.3.1
CIM API Programming Reference
6 CIM Indications 6.1 Overview
6.1
6.2 Fibre Channel Ports
6.1
6.3 Job Control for Copy Services
6.2
6.4 Thin Provisioning
6.2
7 3PAR CIM-API Extensions 7.1 Health Management
7.2
7.1.1
Controller Node Subsystem
7.2
7.1.1.1
Controller Node Subsystem CIM Classes
7.2
7.1.1.2
Properties for TPD_StorageSystem
7.3
7.1.1.3
Properties for TPD_NodeSystem
7.3
7.1.1.4
Properties for TPD_PCICard
7.4
7.1.1.5
Properties for TPD_NodeCPU
7.4
7.1.1.6
Properties for TPD_PhysicalMemory
7.5
7.1.1.7
Properties for TPD_IDEDrive
7.5
7.1.2
7.1.3
7.1.4
Supported Methods
7.5
7.1.2.1
7.6
Disk Enclosure Subsystem
7.6
7.1.3.1
Disk Enclosure Subsystem CIM Classes
7.6
7.1.3.2
Properties for TPD_StorageSystem
7.7
7.1.3.3
Properties for TPD_DriveCage
7.7
7.1.3.4
Properties for TPD_CageInterfaceCard
7.8
7.1.3.5
Properties for TPD_Magazine
7.8
7.1.3.6
Properties for TPD_DiskDrive
7.9
Supported Methods 7.1.4.1
7.1.5
UML Diagram
UML Diagram
7.9 7.10
Power and Cooling
7.10
7.1.5.1
Power and Cooling CIM Classes
7.10
7.1.5.2
Properties for TPD_StorageSystem
7.11
7.1.5.3
Properties for TPD_NodeSystem
7.11
7.1.5.4
Properties for TPD_DriveCage
7.12 Table of Contents
ix
CIM API Programming Reference
InForm OS Version 2.3.1
7.1.6
7.1.5.5
Properties for TPD_PowerSupply
7.12
7.1.5.6
Properties for TPD_Battery
7.13
7.1.5.7
Properties for TPD_Fan
7.13
Supported Methods
7.14
7.1.6.1
7.14
UML Diagram
7.2 Inventory Management 7.2.1
7.2.2
7.2.3
7.2.4
7.2.5
x
Table of Contents
7.15
Controller Node Subsystem
7.15
7.2.1.1
Controller Node Subsystem CIM Classes
7.15
7.2.1.2
Properties for TPD_StorageSystem
7.16
7.2.1.3
Properties for TPD_SystemPackage
7.16
7.2.1.4
Properties for TPD_NodeSystem
7.17
7.2.1.5
Properties for TPD_NodePackage
7.17
7.2.1.6
Properties for TPD_PCICard
7.17
7.2.1.7
Properties for TPD_NodeCPU
7.18
7.2.1.8
Properties for TPD_PhysicalMemory
7.18
7.2.1.9
Properties for TPD_IDEDrive
7.18
Supported Methods
7.19
7.2.2.1
7.19
UML Diagram
Disk Enclosure Subsystem
7.20
7.2.3.1
Disk Enclosure Subsystem CIM Classes
7.20
7.2.3.2
Properties for TPD_StorageSystem
7.20
7.2.3.3
Properties for TPD_DriveCage
7.21
7.2.3.4
Properties for TPD_CageInterfaceCard
7.21
7.2.3.5
Properties for TPD_Magazine
7.22
7.2.3.6
Properties for TPD_DiskDrive
7.22
7.2.3.7
Properties for TPD_DiskDrivePackage
7.22
7.2.3.8
Properties for TPD_DiskSoftwareIdentity
7.23
Supported Methods
7.24
7.2.4.1
7.24
UML Diagram
Power and Cooling
7.25
7.2.5.1
Power and Cooling CIM Classes
7.25
7.2.5.2
Properties for TPD_StorageSystem
7.25
InForm OS Version 2.3.1
CIM API Programming Reference
7.2.6
7.2.5.3
Properties for TPD_NodeSystem
7.26
7.2.5.4
Properties for TPD_DriveCage
7.26
7.2.5.5
Properties for TPD_PowerSupply
7.26
7.2.5.6
Properties for TPD_Battery
7.27
7.2.5.7
Properties for TPD_Fan
7.27
Supported Methods
7.28
7.2.6.1
7.28
UML Diagram
7.3 Thin Provisioning and TPVV Manipulations
A
Managed Object Format Files A.1 3PAR_InterOp.mof
A.2
A.2 3PAR_TPD.mof
A.7
A.3
3PAR_TPDCage.mof
A.65
A.4
PAR_TPDDisk.mof
A.81
A.5 3PAR_TPDNode.mof A.6
IX RH
7.28
A.90
3PAR_TPDEnv.mof
A.101
A.7 3PAR_TPDLocation.mof
A.109
A.8
A.110
3PAR_TPDEthPort.mof
A.9 3PAR_TPDiSCSI.mof
A.113
A.10
A.124
3PAR_TPDStats.mof
Index Revision History
Table of Contents
xi
CIM API Programming Reference
xii
Table of Contents
InForm OS Version 2.3.1
InForm OS Version 2.3.1
CIM API Programming Reference
1 Introduction In this chapter 1.1 Audience
1.1
1.2 Related Documentation
1.2
1.3 Organization
1.2
1.4 Typographical Conventions
1.3
1.5 Advisories
1.4
1.1 Audience To use this document, you must be familiar with basic object oriented development techniques and be familiar with the following:
Storage Management Initiative Specification (SMI-S)
Common Information Model (CIM)
Hypertext Transfer Protocol (HTTP)
Secure Socket Layer (SSL)
CIM Operations over HTTP
Unified Modeling Language (UML)
Introduction
1.1
CIM API Programming Reference
InForm OS Version 2.3.1
1.2 Related Documentation The following documents also provide information related to InServ® Storage Servers and the InForm® Operating System: Table 1-1. Related Documentation
For Information About…
Read the…
Determining InServ Storage Server hardware
3PAR InServ E-Class/F-Class Storage Server
specifications, installation considerations,
Physical Planning Manual
power requirements, networking options, and cabling
3PAR InServ S-Class/T-Class Storage Server Physical Planning Manual
Identifying storage server components and
3PAR InForm OS Messages and Operator’s
detailed alert information
Guide
CLI commands and their usage
InForm OS Command Line Interface Reference
Using the InForm Management Console
3PAR InForm Management Console Online
Graphical User Interface to configure and
Help
administer InServ Storage Servers Using the InForm Command Line Interface (CLI)
3PAR InForm OS CLI Administrator’s Manual
to configure and administer InServ Storage Servers
1.3 Organization This guide is organized as follows:
Chapter 1, Introduction (this chapter), provides an overview of this guide, including information on audience, related documentation, and typographical conventions.
1.2
Chapter 2, Concepts, provides an overview of SMI-S and WBEM Initiatives.
Chapter 3, Security, discusses 3PAR CIM authentication and authorization.
Related Documentation
InForm OS Version 2.3.1
CIM API Programming Reference
Chapter 4, Configuring and Using the CIM Server, explains the steps required to configure the 3PAR CIM Server using the InForm CLI.
Chapter 5, 3PAR CIM API SMI-S Support, provides information on all 3PAR CIM supported profile and subprofiles.
Chapter 6, CIM Indications, describes the indication subscriptions supported by the 3PAR CIM Server.
Chapter 7, 3PAR CIM-API Extensions, discusses additional classes that provide management for InServ Storage Server specific features not covered by SMI-S.
Appendix A, Managed Object Format Files, provides the contents of the Managed Object Format (MOF) files for the InServ Storage Server.
This guide also contains a revision history for your reference.
1.4 Typographical Conventions This guide employs the following typographical conventions: Table 1-2. Typographical Conventions
Typeface
Meaning
Example
ABCDabcd
Used for dialog elements
When prompted, click Finish to
such as titles, button labels,
complete the installation.
and other screen elements. ABCDabcd
ABCDabcd
Used for paths, filenames,
Open the file
and screen output.
\os\windows\setup.exe
Used to differentiate user
# cd /opt/3par/console
input from screen output.
Used for variables in
Modify the content string by adding the -
filenames, paths, and
P option after -jar inform.jar
screen output.
Used for variables in user
#./java -jar inform.jar
input.
-P
Typographical Conventions
1.3
CIM API Programming Reference
InForm OS Version 2.3.1
1.5 Advisories To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this guide.
CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.
WARNING: Warnings alert you to actions that can cause injury to people or irreversible damage to data or the operating system.
1.4
Advisories
InForm OS Version 2.3.1
CIM API Programming Reference
2 Concepts In this chapter 2.1 About SMI-S
2.1
2.2 About the WBEM Initiative
2.2
2.1 About SMI-S SMI-S enables management of Storage Area Networks (SANs) in a heterogeneous, multivendor environment. SMI-S uses an object-oriented model based on the Common Information Model (CIM) to define objects and services which comprise a SAN. By leveraging vendor and technology independent standards, SMI-S allows management application vendors to create applications that work across products from multiple vendors. The SMI-S model is divided into several profiles, each of which describes a particular class of SAN entities (such as disk arrays or Fibre Channel switches). These profiles allow for differences in implementations but provide a consistent approach for clients to discover and manage SAN resources and facilitate interoperability across vendor products within the SAN. SMI-S also defines an automated resource discovery process using Service Location Protocol version 2 (SLPv2). This allows management applications to automatically find SAN resources and then probe them to determine which of the SMI-S profiles and features they support. For more information about SMI-S, refer to the Storage Management Initiative Web site at http://www.snia.org/smi/home.
Concepts
2.1
CIM API Programming Reference
InForm OS Version 2.3.1
2.2 About the WBEM Initiative SMI-S is based on the Web-Based Enterprise Management (WBEM) Initiative, which is defined by the Distributed Management Task Force (DMTF). WBEM is a set of management and Internet standard technologies developed to unify the management of distributed computing environments. The DMTF has developed the following core set of standards that make up WBEM: Table 2-1. Core Standards for WBEM Initiative
Standard
Description
The Common Information Model
The CIM standard is the data model for WBEM. CIM provides
(CIM) standard
a conceptual framework for describing management data for systems, networks, applications and services, and allows for vendor extensions. SMI-S uses CIM to model those objects and relationships that comprise a SAN.
CIM-XML
CIM-XML is a method of exchanging CIM management data. CIM-XML uses an xmlCIM payload and HTTP(s) as the transport mechanism. This protocol is defined by the following specifications:
Specification for the Representation of CIM in XML Defines a standard for the representation of Common Information Model (CIM) elements and messages in XML, written in Document Type Definition (DTD).
CIM Operations over HTTP - Defines a mapping of CIM Messages onto HTTP that allows implementations of CIM to interoperate in an open, standardized manner. It utilizes the CIM XML DTD that defines the XML Schema for CIM objects and messages.
WBEM Discovery using Service
WBEM Discovery using SLP is a method for applications to
Location Protocol (SLP)
identify WBEM-based management systems. For more information regarding WBEM and CIM, refer to the DMTF web site at http://www.dmtf.org.
2.2
About the WBEM Initiative
InForm OS Version 2.3.1
CIM API Programming Reference
3 Security In this chapter 3.1 TCP Ports
3.1
3.2 Authentication
3.2
3.3 Authorization
3.3
3.1 TCP Ports The 3PAR CIM-API uses dedicated TCP ports for CIM-XML communications and server location information. Two ports are specified by the DMTF and registered with IANA for CIM-XML communications between management clients and any CIM Server. The following table lists the TCP Ports for the CIM-XML communication and service location protocols: Table 3-1. TCP Ports for CIM-XML Communication
Protocol
TCP Port
HTTP
5988 (default value)
HTTPS
5989 (default value)
Service Location (SLP)
427
Security
3.1
CIM API Programming Reference
InForm OS Version 2.3.1
3.2 Authentication Authentication verifies the identity of an entity. Management clients accessing the 3PAR CIM Server are authenticated using a request/ challenge mechanism using HTTP Basic authentication. When a request is received from a management client, the CIM Server challenges the client to send a user name and password encoded in the HTTP Authorization header. The user names and passwords used are the same as those used by other management interfaces and are case sensitive. NOTE: 3PAR CIM does not currently support LDAP user name and password authentication; only local user names and passwords are valid. Please see the 3PAR Concepts Guide, Chapter 3 for more information on local versus LDAP user credentials.
The 3PAR CIM Server uses OpenSSL to support HTTPS connections. The server supports SSLv3 and TLSv1 by default and uses the default OpenSSL cipher list only. For more about OpenSSL, refer to http://www.openssl.org/docs. NOTE: Because Basic Authentication means that client user names and passwords are sent over the wire in unencrypted form, it is recommended that the authentication is carried out either over a physically secure private network, or in conjunction with HTTPS.
3.2
Authentication
InForm OS Version 2.3.1
CIM API Programming Reference
3.3 Authorization Authorization determines whether an entity that has already been authenticated is allowed to perform a given operation. The 3PAR CIM Server allows any authenticated user to retrieve CIM class and instance information. However, to invoke methods on CIM classes or instances, you must either have an Edit or Super permission level. Refer to the 3PAR Concepts Guide or the 3PAR InForm OS CLI Administrators Manual for a full discussion on authorization levels.
NOTE: Access to certain information concerning volumes, CPGs, etc., is controlled by the InForm OS. Therefore, if a user authenticates with the CIM API and only has access to certain domains, only those objects in those domains returned by the InForm OS. In addition, operations on those objects also be constrained at the domain level.
Authorization
3.3
CIM API Programming Reference
3.4
Authorization
InForm OS Version 2.3.1
InForm OS Version 2.3.1
CIM API Programming Reference
4 Configuring and Using the CIM Server In this chapter 4.1 CLI Command Overview
4.2
4.2 Enabling and Disabling the CIM Server
4.2
4.2.1 Enabling the CIM Server
4.2
4.2.2 Disabling the CIM Server
4.3
4.4 Displaying the CIM Server Version
4.4
4.5 Communicating with the CIM Server
4.4
4.5.1 Client Software
4.4
4.5.2 Sending Client Requests
4.6
4.6 CIM Namespaces
4.7
This chapter provides information required to configure the 3PAR CIM Server using the InForm CLI.
Configuring and Using the CIM Server
4.1
CIM API Programming Reference
InForm OS Version 2.3.1
4.1 CLI Command Overview The following CLI commands are available to manage the 3PAR CIM Server: Table 4-1. CLI Commands Used to Manage the 3PAR CIM Server
Command
Purpose
Required Permission Level
Sets properties of the CIM Server.
setcim
Super
This command can be used to enable or disable certain services.
showcim
Displays status information for
Any
the CIM Server.
startcim
Enables the CIM Server.
Super
stopcim
Disables the CIM Server.
Super
NOTE: Refer to the 3PAR InForm OS Command Line Interface Reference for additional information.
4.2 Enabling and Disabling the CIM Server By default, the CIM Server is disabled and must be manually enabled by an administrator before it can be used.
4.2.1 Enabling the CIM Server To enable the 3PAR CIM Server, issue the startcim command: # startcim CIM server will start in about 90 seconds.
4.2
CLI Command Overview
InForm OS Version 2.3.1
CIM API Programming Reference
4.2.2 Disabling the CIM Server To disable the 3PAR CIM Server, issue the stopcim command: #stopcim -f CIM server stopped successfully.
If you issue this command without the -f option, you are prompted to confirm your intent to disable the 3PAR CIM Server.
4.3 Displaying the CIM Server Status To display the CIM Server status information, issue the showcim command. If the CIM Server process is running, the following output is displayed: # showcim -Service- -State- --SLP-- SLPPort -HTTP-- HTTPPort -HTTPS- HTTPSPort PGVer CIMVer Enabled Active Enabled 427 Enabled 5988 Enabled 5989 2.5.1 2.3.1
If the CIM Server process is not running, the following output is displayed: # showcim -Service- -State-- --SLP-- SLPPort -HTTP-- HTTPPort -HTTPS- HTTPSPort PGVer CIMVer Enabled Inactive Enabled 427 Enabled 5988 Enabled 5989 2.5.1 2.3.1
The showcim command enables you to view the overall status of the CIM Server; the status and ports used for the HTTP, HTTPS, and SLP; the version of the internal Pegasus CIM Object Manager; and the version of the CIM Server.
Displaying the CIM Server Status
4.3
CIM API Programming Reference
InForm OS Version 2.3.1
4.4 Displaying the CIM Server Version The CIM Server version can be displayed using the showcim command as shown previously, or by using the showversion -a command. # showversion -a Release version 2.3.1 Patches: None Component Name CLI Server CLI Client GUI Server System Manager Kernel TPD Kernel Code Utilities Software Updater CIM Server
Version 2.3.1 2.3.1 2.3.1 2.3.1 2.3.1 2.3.1 2.3.1 2.3.1 2.3.1
4.5 Communicating with the CIM Server Several methods of communicating with the CIM Server are listed as follows:
4.5.1 Client Software 3PAR does not provide client software, but commercial and open source CIM client software packages are readily available. Table 4-2 lists some of the available tools and packages.
4.4
Displaying the CIM Server Version
InForm OS Version 2.3.1
CIM API Programming Reference
Table 4-2. Available Client Software Tools and Packages
Tool or Package
Description
URL
CIMNavigator
CimNavigator is a graphical
http://www.cimnavigator.com/
browser tool written in Java that can be used to manipulate CIM objects hosted on CIMOMs on remote or local computers. 3PAR uses this tool for internal development and testing. WBEM Services
The WBEM Services project is
http://
an open-source Java
wbemservices.sourceforge.net
implementation of Web Based Enterprise Management. This project consists of APIs, server and client applications and tools. Ultimate CIM
Ultimate CIM is the Eclipse
http://sourceforge.net/projects/
plug-in that enables
ultimatecim/
developers to explore CIMOM, walk associations, execute WQL queries, graphically view class hierarchy and more.
Communicating with the CIM Server
4.5
CIM API Programming Reference
InForm OS Version 2.3.1
4.5.2 Sending Client Requests Management clients send requests to the 3PAR CIM Server. A valid client request must include:
A properly formed HTTP header.
A request must be addressed to the CIM Server on an InServ Storage Server.
This address consists of an IP Address and the appropriate TCP port for either HTTP or HTTPS as shown in the table that follows:
Protocol
TCP Port
HTTP
5988 (default value)
HTTPS
5989 (default value)
The desired operation and its required parameters. For information about CIM operations, please refer to CIM Operations over HTTP.
The object or objects on which the operation is to be performed. The payload of the client request is XML. For information about XML coding for CIM, refer to Representation of CIM in XML.
4.6
Communicating with the CIM Server
InForm OS Version 2.3.1
CIM API Programming Reference
4.6 CIM Namespaces CIM namespaces are logical groupings of CIM classes and CIM instances that represent managed objects in a particular environment. When making requests of a CIM server, a client application must include the namespace that contains those classes. The namespace is case insensitive. Table 4-3 provides information about the namespaces supported by the 3PAR CIM Server: Table 4-3. 3PAR CIM Server Supported Namespaces
Namespace
Purpose
root/PG_Interop
This is the Interop Namespace as defined in SMI-S. The Interop Namespace is used to find Registered Profiles and other CIM classes related to the SMI-S Server Profile.
root/tpd
The root/tpd namespace (ThreeParData) is used to uniquely identify CIM Servers supplied by 3PAR Inc. and provides management of all classes related to managing the InServ Storage Server.
CIM Namespaces
4.7
CIM API Programming Reference
4.8
CIM Namespaces
InForm OS Version 2.3.1
InForm OS Version 2.3.1
CIM API Programming Reference
5 3PAR CIM API SMI-S Support In this chapter 5.1 Standard Compliance
5.2
5.2 SMI-S Functionality
5.2
5.3 Discovery Service
5.3
5.4 Supported Profiles
5.3
5.5 Supported Array Packages
5.3
5.6 Supported Array Subprofiles
5.4
5.7 Server Profile
5.6
5.8 Array Profile
5.8
5.9 Block Services Package
5.9
5.10 Copy Services Subprofile
5.56
5.11 Location Subprofile
5.95
5.12 Multiple Computer System Subprofile
5.96
5.13 Software Subprofile
5.97
5.14 Masking and Mapping Subprofile
5.98
5.15 HideLUsFromStorageHardwareIDCollection (Removing Host-Sees VLUNs)
5.121
3PAR CIM API SMI-S Support
5.1
CIM API Programming Reference
InForm OS Version 2.3.1
5.16 FC Target Ports Subprofile
5.132
5.17 FC Initiator Ports Subprofile
5.132
5.18 iSCSI Target Ports Subprofile
5.133
5.19 Disk Drive Lite Subprofile
5.135
5.20 Block Server Performance Subprofile
5.137
The 3PAR CIM API supports the Storage Management Initiative Specification. The CIM API also supports extensions to these profiles to provide features that are not available from the standard profiles.
5.1 Standard Compliance The 3PAR CIM Server has successfully completed testing and conforms to elements of the Storage Networking Industry Association’s Conformance Testing Program (SNIA-CTP) for the SMI specification. For detailed information, please refer to: http://www.snia.org/forums/smi/tech_programs/ctp/conformingproviders/ 3PAR.html
5.2 SMI-S Functionality SMI-S defines a number of services, profiles, and subprofiles that are used to manage elements of a SAN. Each InServ Storage Server running InForm OS version 2.2.3 and beyond comes with an embedded CIM Server that includes support for the profiles, subprofiles, and services as described in the following sections.
5.2
Standard Compliance
CIM API Programming Reference
5.3 Discovery Service Table 5-1 lists the Discovery Service that is supported: Table 5-1. Discovery Service
Service
Version
Purpose
Service Location
SLPV2
Allows management applications to discover the location
Protocol (SLP)
of CIM Servers and the supported capabilities of those servers.
5.4 Supported Profiles Table 5-2 lists supported profiles. Table 5-2. Supported Profiles
Profile
Version
Purpose
Server Profile
1.1.0
Defines the capabilities of the CIM Server, including the supported SMI-S Profiles and Subprofiles supported.
Array Profile
1.1.0
Describes RAID arrays and disk storage systems.
5.5 Supported Array Packages Table 5-3 lists the supported packages that are mandatory for the Profiles in which they appear: Table 5-3. Supported Array Packages
Package
Version
Purpose
Block Services
1.1.0
Provides management of StorageVolumes and
StoragePools.
Discovery Service
5.3
CIM API Programming Reference
InForm OS Version 2.3.1
5.6 Supported Array Subprofiles Table 5-4 lists the Supported Array Subprofiles: Table 5-4. Supported Array Subprofiles
Subprofile
Version
Purpose
Location
1.1.0
Provides information about the physical location of a disk storage system.
Multiple
1.1.0
Provides information about the multiple computer systems
Computer
(controller nodes) that cooperate to present a virtual computer
System
system (cluster).
Software
1.1.0
Provides information on installed controller software.
Masking and
1.1.0
Provides management of LUNs.
1.1.0
Provides management of front end (host facing) Fibre Channel
Mapping FC Target Ports
ports. FC Initiator
1.1.0
Provides management of back end (disk enclosure) FC ports.
1.1.0
Provides management of front end (host facing) iSCSI ports.
Disk Drive Lite
1.1.0
Provides management of disk drive devices.
Block Server
1.1.0
Provides performance statistics information for block servers.
1.1.0
Provides management of physical and virtual copies (remote
Ports iSCSI Target Ports
Performance Copy Services
copy is not supported). Job Control
5.4
1.1.0
Supported Array Subprofiles
Provides management of tasks related to Copy Services.
CIM API Programming Reference
5.6.1 SMI-S Support by Release Table 5-5 provides information on the level of SMI-S support for each of the releases of the CIM Server. Table 5-5. Supported SMI-S Levels by Release
SMI-S Version
Profile
Subprofile or
Release Version
Package
1.0.2
2.2.2
2.2.3
2.2.4
2.3.1
Server Profile
X
X
X
X
Array Profile
X
X
X
X
X
X
X
X
Server Profile
X
X
X
X
Array Profile
X
X
X
X
Software
X
X
X
X
Block Services
X
X
X
X
Masking and
X
X
X
X
FC Target Ports
X
X
X
X
FC Initiator Ports
X
X
X
X
Location
X
X
X
X
Multiple
X
X
X
X
Disk Drive Lite
X
X
X
X
iSCSI Target Ports
X
X
X
X
X
X
X
Software 1.1.0
Mapping
Computer System
Block Server Performance
Supported Array Subprofiles
5.5
CIM API Programming Reference
InForm OS Version 2.3.1
Table 5-5. Supported SMI-S Levels by Release (continued)
SMI-S Version
Profile
Subprofile or
Release Version
Package 2.2.2
2.2.3
2.2.4
2.3.1
Copy Services
X
Job Control
X
5.6.2 Discovery Service The first step in managing an SMI-S enabled SAN is to discover its available resources (such as the CIM servers). SMI-S defines Service Location Protocol v2 (SLPv2) as the discovery mechanism. CIM clients use SLP to query for available CIM servers. CIM servers answer with generic information about what services they provide and the URL at which these services reside.
5.7 Server Profile A CIM Server is anything that supports the CIM-XML protocol and supports the basic read functional profile as defined by the CIM Operations over HTTP specification. After a CIM client has discovered a CIM server within a SAN, it then needs to determine the services provided by that server. The Server Profile defines the capabilities of the CIM Server. This includes the communication mechanisms the CIM Server supports, the CIM namespaces that it manages, and the SMI-S profiles and subprofiles that are supported. For a complete discussion on the Server Profile model, please refer to SMI-S at http://www.snia.org.
5.6
Server Profile
CIM API Programming Reference
5.7.1 Server Profile CIM Classes Table 5-6 Lists the key Server Profile CIM classes: Table 5-6. Server Profile CIM Classes
CIM Class
Description
TPD_CIMXMLCommunicationMechanism
Defines the communication protocols supported by the CIM server.
TPD_Namespace
Defines the CIM namespaces supported by the CIM Server.
TPD_ObjectManager
The CIM Object Manager service of the CIM Server.
TPD_RegisteredProfile
One instance of this class exists for each SMI-S Profile that is registered with the CIM Server.
TPD_RegisteredSubprofile
One instance of this class exists for each SMI-S Subprofile that is registered with the CIM Server.
TPD_StorageSystem
The storage server that is hosting the CIM Server.
5.7.2 Supported Methods Table 5-7 describes the currently supported method for TPD_StorageSystem:
Table 5-7. Method for TPD_StorageSystem
Method
Description
modifyInstance()
Provides the ability to set owner and contact information for the
StorageSystem.
Server Profile
5.7
CIM API Programming Reference
InForm OS Version 2.3.1
5.8 Array Profile The Array profile models the physical and logical aspects of disk storage systems. The basic Array profile provides a high level, read-only 'view' of a storage system. The mandatory Block Services package and the various optional subprofiles extend this description and provide additional management capabilities. For detailed information regarding the Array profile, refer to SMI-S at http://www.snia.org.
5.8.1 Array Profile CIM Classes Table 5-8 shows the CIM class for the Array profile: Table 5-8. Array Profile CIM Class
Class
Description
TPD_StorageSystem
Represents the storage array as a whole. The Dedicated property indicates this system operates as a storage array.
5.8.2 Supported Methods Table 5-9 shows the supported method for TPD_StorageSystem: Table 5-9. Method for TPD_StorageSystem
Method
Description
modifyInstance()
Provides the ability to set owner and contact information for the StorageSystem.
5.8
Array Profile
CIM API Programming Reference
5.9 Block Services Package The Block Services package defines standards for viewing/managing storage capacity. This includes managing StoragePools and allocating capacity from StoragePools to be used by external consumers. With regards to 3PAR, implementation of this package provides the ability to manage Storage Volumes on the InServ Storage Server. For detailed information regarding the Block Services package, refer to SMI-S at http://www.snia.org.
5.9.1 Block Services Package CIM Classes Table 5-10 shows the key Block Services Package CIM classes: Table 5-10. Block Services Package CIM Classes
Class
Description
TPD_StorageSystem
Represents the storage array as a whole.
TPD_StorageVolume
Storage volumes that are equivalent to SCSI Logical Units visible to consumers.
TPD_StoragePool
Allocatable space on the array.
TPD_StorageSetting
Used by clients as input to the StorageConfigurationService, StorageSetting describes the desired configuration of Storage Volumes.
TPD_StorageCapabilities
Provides information about the possible configuration parameters for elements created from a given StoragePool.
TPD_StorageConfigurationCapabilities
Provides information about what storage configuration functionality is provided by StorageConfigurationService.
Block Services Package
5.9
CIM API Programming Reference
InForm OS Version 2.3.1
Table 5-10. Block Services Package CIM Classes (continued)
Class
Description
TPD_StorageConfigurationService
Allows clients to configure Storage Volumes.
TPD_DynamicStoragePool
Storage Pool representing a Common Provisioning Group (CPG).
5.9.2 Supported Methods Table 5-11 - Table 5-14 shows the supported methods for the Block Services Package:
Table 5-11. Methods for TPD_StorageCapabilities
Method
Description
CreateSetting()
Provides the ability to create StorageSetting objects for use in creating StorageVolumes.
GetSupportedStripeLengthRange()
Returns the possible stripe lengths for this capability.
GetSupportedStripeDepths()
Returns the possible stripe depths for this capability.
Table 5-12. Methods for TPD_StorageSetting
Method modifyInstance()
Description Provides the ability to modify a StorageSetting for use in creating StorageVolumes.
deleteInstance()
5.10
Block Services Package
Provides the ability to delete a StorageSetting.
CIM API Programming Reference
Table 5-13. Methods for TPD_StorageConfigurationService
Method
Description
CreateOrModifyElementFromStoragePool()
Provides the ability to create or modify StorageVolumes using a specific StorageSetting from a source StoragePool.
ReturnToStoragePool()
Provides the ability to remove StorageVolumes, returning the capacity to the original StoragePool.
CreateOrModifyStoragePool()
Provides the ability to create or modify DynamicStoragePool using a specific StorageSetting from a source StoragePool.
DeleteStoragePool()
Provides the ability to remove DynamicStoragePool, returning the capacity to the parent StoragePool.
Table 5-14. Method for TPD_StoragePool
Method
Description
GetSupportedSizeRanges()
Returns the supported size ranges for elements allocated from this Pool.
Block Services Package
5.11
CIM API Programming Reference
InForm OS Version 2.3.1
5.9.3 StorageSetting There are eight types of StorageSetting: 1
Pre-created StorageSetting for creating legacy or fully provisioned virtual volumes. There are three of these, one for each RAID type, and each is associated to 3PAR:Capabilities:RAIDx StorageCapabilities. Their InstanceIDs are 3PAR:StorageSetting:RAIDx. A client can use StorageSetting to create a legacy or fully provisioned virtual volume. Most Logical Disk (LD) and virtual volume-specific properties are populated. For InForm OS release 2.3.1, a fourth instance is added for RAID-60.
2
Pre-created StorageSetting for creating DynamicStoragePool. There are three of these, one for each RAID type, and each is associated to 3PAR:Capabilities:RAIDx StorageCapabilities. Their InstanceIDs are 3PAR:DynamicStoragePoolSetting:RAIDx. A client can use this StorageSetting to create a DynamicStoragePool. Most LD properties are populated, but not those for virtual volumes. For InForm OS release 2.3.1, a fourth instance is added for RAID-60.
3
Pre-created StorageSetting for creating Thinly Provisioned Virtual Volumes (TPVVs). There are three of these, one for each RAID type, and each is associated to 3PAR:Capabilities:RAIDx StorageCapabilities. Its InstanceID is 3PAR:ThinProvisionedVolumeSetting:RAIDx. A client can use this StorageSetting for creating a Thinly Provisioned (TP) virtual volume. Only virtual volume-related properties are populated. For InForm OS release 2.3.1, a fourth instance is added for RAID-60.
4
Current StorageSetting of a virtual volume. This StorageSetting contains the current configuration of a virtual volume. If the virtual volume is a legacy volume, this Setting has a StorageSettingAssociatedToCapabilities association to the 3PAR:Capabilities:RAIDx capabilities. If the virtual volume user space draws from a DynamicStoragePool (DSP), then this Setting has a StorageSettingAssociatedToCapabilities association to the “3PAR:Current Capabilities for DynamicStoragePool StorageCapabilities” of the DSP.
5
StorageSetting generated from “CreateSetting of 3PAR:Capabilities:RAIDx” capabilities. StorageSetting created this way is generic enough that it encompasses LD, virtual volume and snap space specific properties. A client has to tailor the properties carefully to create the element (DSP, legacy volume or new-style volume) it desires. This Setting has a
5.12
Block Services Package
CIM API Programming Reference
StorageSettingGeneratedFromCapabilities association to the “3PAR:Capabilities:RAIDx”capabilities. 6
StorageSetting generated from CreateSetting of “3PAR:Current Capabilities for DynamicStoragePool” Capabilities. StorageSetting created this way can be used by a client for user space or snap space of a virtual volume. By default the ThinlyProvisioned property is set to FALSE. A client has to modify this to TRUE if a TPVV is desired. This setting has a StorageSettingGeneratedFromCapabilities association to the “3PAR:Current Capabilities for DynamicStoragePool:RAIDx” Capabilities.
7
StorageSetting created by CreateInstance. These StorageSetting contain values that are totally determined by the client who created it. The most likely usage for this is if a client clones an existing fixed StorageSetting and then modified some of the property values before creating it. This Setting has a StorageSettingGeneratedFromCapabilities association to the appropriate “3PAR:Capabilities:RAIDx” Capabilities according to the RAID type of the
StorageSetting.The default is RAID10. 8
Persistent StorageSetting/template. StorageSetting (templates) that are stored in PR. The TemplateType and TemplateForVolumeType properties of the StorageSetting restrict what kind of element creation this setting can be applied to. This Setting has a StorageSettingGeneratedFromCapabilities association to the appropriate “3PAR:Capabilities:RAIDx” Capabilities according to the RAID type of the
StorageSetting.The Default is RAID10. Relevant Properties of StorageSetting
Properties
Description
Uint64 AllocationUnit
Grow increment in bytes. When a TP StorageVolume or a DynamicStoragePool grows on demand, the system allocates this number of bytes on each allocation.
Uint64 AllocationUnitMax
Maximum allocation unit in bytes.
Uint64
Minimum allocation unit in bytes.
AllocationUnitMin
Block Services Package
5.13
CIM API Programming Reference
InForm OS Version 2.3.1
Relevant Properties of StorageSetting (continued)
Properties
Description
Uint64
Snap space limit in bytes. If SpaceLimit (in bytes) is greater
SpaceLimit
than zero, the space consumed by the storage element shall not exceed the value of SpaceLimit. For TP StorageVolume, if SpaceLimit is zero, allocation limit is not enforced (e.g. the volume can grow until the system runs out of space).
Uint16
Snap space limit warning in percentage of SpaceLimit.
SpaceLimitWarning
When actual space allocated to the TP StorageVolume or
Threshold
DynamicStoragePool hits this threshold, alerts are generated. For example, if SpaceLimitWarningThreshold is 90% and SpaceLimit is 100GB, alerts are generated when allocated space is 90GB or more.
Uint64
User space limit in bytes. If UserSpaceLimit (in bytes) is
UserSpaceLimit
greater than zero, the space consumed by the storage element shall not exceed the value of UserSpaceLimit. For TP StorageVolume, if UserSpaceLimit is zero, allocation limit is not enforced (e.g. the volume can grow until the system runs out of space).
Uint16
User space limit warning in percentage of UserSpaceLimit.
UserSpaceLimitWarning
When the actual space allocated to the TP StorageVolume or
Threshold
DynamicStoragePool hits this threshold, alerts are generated. For example, if UserSpaceLimitWarningThreshold is 90% and UserSpaceLimit is 100GB, alerts are generated when allocated space is 90GB or more.
5.14
Block Services Package
CIM API Programming Reference
Relevant Properties of StorageSetting (continued)
Properties
Description
Uint32
TP volume user space allocation warning in percentage of
UserSpaceAllocationWarning
volume size. If this is set, UserSpaceLimitWarningThreshold is ignored. UserSpaceLimitWarningThreshold calculation requires UserSpaceLimit, which may not be specified. UserSpaceAllocationWarning thus allows a percentage to be specified without requiring UserSpaceLimit to be specified (in CLI, one can specify –usr_aw option without specifying –usr_al option). Applies only to TPVVs.
Uint32 SnapSpaceAllocationWarning
Volume snap space allocation warning in percentage of volume size. If this is set, SpaceLimitWarningThreshold is ignored. SpaceLimitWarningThreshold calculation requires SpaceLimit, which may not be specified. SnapSpaceAllocationWarning thus allows a percentage to be specified without requiring SpaceLimit to be specified (in CLI, one can specify –snp_aw option without specifying –snp_al option).
Uint64
Warning alert is issued if snap space of a CPG exceeds
DSPSnapSpaceGrowWarning
DSPSnapSpaceGrowWarning. 0 means no warning limit is enforced. This value is in bytes. Applies to DynamicStoragePool only.
Uint16
Describes how the elements are used. For example, if a new
IntendedUsage
TP StorageVolume is used for snap shot, this value is 7. The default value is 0 (“not specialized”).
Block Services Package
5.15
CIM API Programming Reference
InForm OS Version 2.3.1
Relevant Properties of StorageSetting (continued)
Properties
Description
Uint16
Generates a low space indication and applies only when
LowSpaceWarningThreshold
creating a DynamicStoragePool. If non-zero, a low space indication is generated when RemainingManagedSpace
of DynamicStoragePool
