3PAR CIM API Programming Reference for InForm OS 2.3.1 3PAR Inc. 4209 Technology Drive Fremont, CA 94538 U.S.A. Part No.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
CIM API Programming Reference xii Table of Contents InForm OS Version 2.3.
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.
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.
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.
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.
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.
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.
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.
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.
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.
CIM API Programming Reference 3.4 Authorization InForm OS Version 2.3.
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.
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.
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.
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.
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.
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.
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.
CIM API Programming Reference 4.8 CIM Namespaces InForm OS Version 2.3.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
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).
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.
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 <= (TotalManagedSpace of DynamicStoragePool*LowSpaceWarningThreshold)/ 100. If it is zero, no indication is generated. Unit is in percentage.
CIM API Programming Reference Table 5-15.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-15.
CIM API Programming Reference If generating a StorageSetting, a client should invoke the CreateSetting method on one of the StorageCapabilties with InstanceID=”3PAR:Capabilities:RAIDx”. By default, StorageSetting.ThinProvisionedPoolType is set to ThinlyProvisionedLimitlessStoragePool(9), which creates a DSP with limitless capacity. The size parameter to CreateOrModifyStoragePool is ignored.
CIM API Programming Reference InForm OS Version 2.3.1 Job - Is always NULL. Goal - This is an instance of StorageSetting describing characteristics of the desired DynamicStoragePool. If it’s NULL, the provider picks the default setting. The ThinProvisionedPoolType property specifies what type of DSP to create: (ThinlyProvisionedQuotaStoragePool(8) for a DSP with an upper limit, or ThinlyProvisionedLimitlessStoragePool(9) for a DSP with no upper bound).
CIM API Programming Reference Table 5-16. DynamicStoragePool Possible Return Values (continued) ValueMap Values 4 Failed 5 Invalid parameter 6 In Use 4097 Size Not Supported Explanation/Notes 5.9.4.1 Relevant Properties of DynamicStoragePool Table 5-17. Relevant Properties of DynamicStoragePool Properties Description string A unique ID within the storage array. The user’s defined PoolID name is used as an identifier.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-17. Relevant Properties of DynamicStoragePool (continued) Properties Description Uint16 Defines the approach associated with the pool for SpaceLimitDetermination determining capacity information for the pool. Allocated (2) means that the advertised capacity is the same as the actual capacity. Quota (3) means that there is an administratively defined limit (SpaceLimit) on the capacity that may be used to create or expand child elements.
CIM API Programming Reference Table 5-17. Relevant Properties of DynamicStoragePool (continued) Properties Description Uint64 This is the nominal number of bytes allocated on disk ConsumedSnapAdminSpace for Snapshot admin (SA) of this pool, not including RAID (bytes) overhead. Uint64 This is the actual number of bytes allocated on disk for ConsumedSnapAdminSpace SA space of this pool, including RAID overhead.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-18. Summary of Modifiable StorageSetting Properties for DSP CLI StorageSetting Property Equivalence SpaceLimit -sdgl SpaceLimitWarningThreshold/ -sdgw DSPSnapSpaceGrowWarning Comment If both the DSPSnapSpaceGrowWarning and SpaceLimitWarningThreshold properties are specified, DSPSnapSpaceGrowWarning takes precedence.
CIM API Programming Reference Table 5-18. Summary of Modifiable StorageSetting Properties for DSP (continued) CLI StorageSetting Property Equivalence Comment ChunkletLocationPreference -ch Disk pattern properties -p e.g. DiskPrimPathNodes, DiskPrimRPM, etc. Corresponding Template -templ Only if using persistent StorageSetting, properties i.e., template. ThinProvisionedPoolType Only Quota (if sdgl is specified) and Limitless (if no sdgl is specified) are supported. 5.9.4.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-19. Instances for StoragePoolConfigurationCapabilities Storage PoolConfigurationCapabilities SupportedSynchronous Primordial Pool ConcretePool DynamicStoragePool DeltaReplica StoragePool NULL Storage Pool Storage Element NULL Creation (2), Creation (5), Storage Storage Pool Element Return (6), Deletion (3), Storage Element Storage Pool Modification (7). Actions Modification (4).
CIM API Programming Reference Additionally, you can use the intrinsic method with the TPD_StorageSetting class. The ModifyInstance method is used to modify the StorageSetting properties that are returned by the CreateSetting method. Beginning with InForm OS 2.3.1, a new method TPD_CreateOrModifyElementFromStoragePools can also be used to create, modify, and grow virtual volumes.
CIM API Programming Reference InForm OS Version 2.3.1 5.9.5.1 Supported Method For Creating a Storage Volume Table 5-20 describes the supported method for creating a volume: Table 5-20. Method for TPD_StorageConfigurationService Method Description CreateOrModifyElementFromStorage Allows clients to create a StorageVolume. Pool() 5.9.5.1.1 Method Signature The method signature for InForm OS 2.2.
CIM API Programming Reference The method signature for InForm OS 2.3.
CIM API Programming Reference InForm OS Version 2.3.1 Size: As an input, this is the desired logical size in bytes of the StorageVolume. If it is not possible to create a volume of the desired size, a return code of Size not supported is returned with the size set to the nearest supported size. If it’s a growing volume request, the size is the new size of the volume. As an output, size is the actual size allocated for the volume.
CIM API Programming Reference Table 5-21. Return Values for CreateOrModifyElementFromStoragePool() ValueMap Values 5 Invalid Parameter 4097 Size Not Supported Explanation/Notes A volume with the specified size cannot be created or grown. 5.9.5.2 Creating Data and Snapshot Space from Two Storage Pools Table 5-22 shows the supported method for creating data and snapshot space from two storage pools: Table 5-22.
CIM API Programming Reference InForm OS Version 2.3.1 uint32 TPD_CreateOrModifyElementFromStoragePools ( [In] String ElementName, [In, Values {“StorageVolume”,“ThinlyProvisionedStorageVolume”}, ValueMap{”2”, “5”}] Uint16 ElementType, [Out] CIM_ConcreteJob ref Job, [In] CIM_StorageSetting ref Goal, [In] CIM_StoragePool ref InPools[], [In, Out] Uint64 Size, [In, Out] CIM_LogicalElement ref TheElement); ElementName: The name of the TP StorageVolume (TPVV) or StorageVolume (CPVV) to be created.
CIM API Programming Reference Size: As an input, this is the desired logical size in bytes of the TP StorageVolume or the requested size of the StorageVolume. If it is a modification request, “Size” is the new size which must be greater than the existing size (e.g. volume can grow, but can not shrink). For TP StorageVolume, the system actually allocates only minimum disk space to back up the volume. More space is allocated on demand as more write data occur.
CIM API Programming Reference InForm OS Version 2.3.1 5.9.5.3 CreateSetting Table 5-24 shows the method forTPD_StorageCapabilities.CreateSetting: . Table 5-24. Method for TPD_StorageCapabilities.CreateSetting Method Description CreateSetting() Allows clients to create a new StorageSetting instance based on existing instances. This method returns a new instance to the client with default property values. There are four instances of StorageCapabilities (one for each RAID type).
CIM API Programming Reference Table 5-25 shows the possible return values for CreateSetting(): Table 5-25. Return Values for CreateSetting () ValueMap Values 0 Method Completed OK 4 Failed 5 Invalid Parameters Explanation/Notes 5.9.5.4 Creating a Volume with a Default Setting A volume can be created using one of the fixed StorageSetting from the four available RAID types. The volume is then created with the default values associated with each RAID type.
CIM API Programming Reference InForm OS Version 2.3.1 to obtain the instance of the TPD_StorageSetting in order to examine the properties. If the values are OK, then it should be used as the ‘Goal’ parameter for the CreateOrModifyElementFromStoragePool method. If not, continue with the next step. 2 If you would like to change the value of some or all of the properties in the TPD_StorageSetting instance from step 1, then you should call the ModifyInstance method to modify them.
CIM API Programming Reference . Table 5-26. Parameters for the CreateOrModifyElementFromStoragePool Method Operations/Parameters Create Volume Grow/Set Volume ElementName Name of Volume New name of volume; NULL means no change in volume name. ElementType Goal Size (bytes) 2 (Storage Volume) 2 5 (Thinly Provisioned Storage 5 (Thinly Provisioned Storage Volume) Volume).
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-27.
CIM API Programming Reference - – an item is a range of integers 5.9.5.7 Summary of Different Types of Volumes That Can Be Created Table 5-28 outlines the types of volumes that are created based on the input InPool and Goal parameter to CreateOrModifyElementFromStoragePool()or InPools and Goal parameter to TPD_CreateOrModifyElementFromStoragePools(). Block Services Package 5.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-28. Volumes Created Based on Parameters to CreateOrModifyElementFromStoragePool() Type of Volume Created CreateOrModifyElementFrom TPD_CreateOrModify StoragePool ElementFromStorage Pools Legacy volume, where user space draws from “3PAR:all-FC” (default), “3PAR:all-NL”, or “3PAR:all-SSD” [3.1.1] concrete pool. 1 ElementType == NULL or Not supported. StorageVolume (2). 2 InPool == NULL or concrete pool.
CIM API Programming Reference Table 5-28. Volumes Created Based on Parameters to CreateOrModifyElementFromStoragePool() Type of Volume Created CreateOrModifyElementFrom TPD_CreateOrModify StoragePool ElementFromStorage Pools Legacy CPVV, where user space draws from “3PAR:all-FC” (default), “3PAR:all-NL”, or “3PAR:all-SSD” [3.1.1] 1 ElementType == NULL or Not supported. StorageVolume (2). 2 InPool == NULL or concrete pool. 3 Goal.DSPName property set. pool. Snap space draws from the DSP. Goal.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-28. Volumes Created Based on Parameters to CreateOrModifyElementFromStoragePool() Type of Volume Created CreateOrModifyElementFrom TPD_CreateOrModify StoragePool ElementFromStorage Pools Fully-provisioned CPVV, where user space and 1 ElementType = NULL or StorageVolume (2). snap space draw from 2 InPool = DSP. the same DSP or two 3 Goal.DSPName property set. If different DSPs.
CIM API Programming Reference Table 5-28. Volumes Created Based on Parameters to CreateOrModifyElementFromStoragePool() Type of Volume Created CreateOrModifyElementFrom TPD_CreateOrModify StoragePool ElementFromStorage Pools Thinly provisioned volume, where user space draws from DSP. Thinly provisioned 1 ElementType = ThinlyProvisionedStorageVo lume(5). 1 ElementType = ThinlyProvisionedSt orageVolume (5). 2 InPool = DSP. 2 InPool = DSP. 3 Goal == NULL or DSPName 3 Goal can be NULL.
CIM API Programming Reference InForm OS Version 2.3.1 5.9.5.8 Modifiable StorageSetting Properties for StorageVolume When creating or modifying a thin-provisioned or full-provisioned StorageVolume, a client can change the following properties of a StorageSetting meant for the user space of the volume to a non-default value. The provider ignores all other properties. Table 5-29 provides a summary of modifiable StorageSetting properties for StorageVolume: Table 5-29.
CIM API Programming Reference Table 5-29. Summary of Modifiable StorageSetting Properties for StorageVolume ExpirationTime [2.3.1] -exp Time when the volume expires. (In CLI, the value is the delta, whereas here it is the actual date and time.) RetentionTime [2.3.1] -retain Time when the volume retention ends. (In CLI, the value is the delta, whereas here it is the actual date and time.) Block Services Package 5.
CIM API Programming Reference InForm OS Version 2.3.1 5.9.6 Calculating Capacity for StoragePool and StorageVolume Calculate capacity for StoragePool and StorageVolume through one of the following methods. 5.9.6.1 Primordial Storage Pool The primordial pool represents the raw capacity of the array. Its TotalManagedSpace therefore represents the capacity of all the disk drives in the array, whether admitted or not, minus capacity lost due to chunklet formatting.
CIM API Programming Reference the creation of the pool can be calculated by (TPD_AllocatedFromStoragePool.SpaceConsumed –DynamicStoragePool.TotalManagedSpace). TotalManagedSpace for a DSP represents the logical capacity that can be used to create storage volumes or delta replica storage pool. RemainingManagedSpace for a DSP represents what logical capacity is available for creating a new volume or delta replica storage pool.
CIM API Programming Reference InForm OS Version 2.3.1 The usable size of the volume, in bytes, is represented by TPD_StorageVolume.ConsumableBlocks multiplied by TPD_StorageVolume.BlockSize. Capacity used for metadata in the creation of the storage volume can be calculated by [(TPD_StorageVolume.NumberOfBlocks minus the TPD_StorageVolume.ConsumableBlocks) multiplied by the TPD_StorageVolume.BlockSize]. For InForm OS release 2.3.1, meaning of StorageVolume.
CIM API Programming Reference 5.9.6.4.2 Before Volume Creation Now the total raw capacity of the all-FC concrete pool is 813896302592 bytes (776192 MB). The Overhead/Metadata used in the creation of the concrete pool (for example, TOC) can be inferred by the difference between this value and TPD_AllocatedFromStoragePool.SpaceConsumed between the primordial and concrete pools.
CIM API Programming Reference InForm OS Version 2.3.1 Concrete TPD_StoragePool.RemainingManagedSpace = previous RemaningManagedSpace value – volume raw size = 813896302592 – 21474836480 = 792421466112. InForm OS 2.3.1: TPD_StorageVolume.NumberOfBlocks = TPD_StorageVolume.ConsumableBlocks = (10240 * 1024 * 1024) / BlockSize = 20971520 (logical size of the volume). TPD_StorageVolume.NumberOfRawBlocks = (20480 * 1024 * 1024) / BlockSize = 41943040 (raw size of the volume).
CIM API Programming Reference TPD_StorageVolume.ConsumableBlocks is set to be the same as TPD_StorageVolume.NumberOfBlocks. Example: Initial State A dynamic storage pool has a virtual capacity of 100GB (as set in the –sdgl option). This value is reflected in the TPD_DynamicStoragePool.SpaceLimit property and is what’s available for volume allocation. Let’s assume that there are no volumes or DeltaReplicaStoragePool allocated from this pool initially.
CIM API Programming Reference InForm OS Version 2.3.1 TPD_DynamicStoragePool.RemainingManagedSpace = TPD_DynamicStoragePool.SpaceLimit – volume logical size = 100G – 10G = 90G TotalManagedSpace for the dynamic storage pool remains unchanged. 5.9.6.6 Thinly Provisioned Storage Volume TPD_AllocatedFromStoragePool.SpaceConsumed between the parent dynamic storage pool and the thinly provisioned storage volume represents the actual size allocated to the volume.
CIM API Programming Reference are actually allocated to the volume may not be the full 10G (let us assume it is 4G). The actual allocated value is represented in the TPD_StorageVolume class as ProvisionedConsumableBlocks. AllocatedFromStoragePool.SpaceConsumed between StorageVolume and the parent DynamicStoragePool is the capacity that is actually allocated to the volume, i.e., AllocatedFromStoragePool.SpaceConsumed is equal to StorageVolume.ProvisionedConsumableBlocks.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-30. Properties Relevant to TPVV Properties Description Uint64 The logical size of the TPVV, in blocks. NumberOfBlocks Uint64 Total number of logically contiguous blocks NumberOfRawBlocks including overhead and metadata, of size Block Size, which form this Extent. The total size of the Extent can be calculated by multiplying BlockSize by NumberOfRawBlocks. If the BlockSize is 1, this property is the total size of the Extent.
CIM API Programming Reference Table 5-30. Properties Relevant to TPVV (continued) Properties Description Uint32 Generate a warning alert when user space of the UserAllocationWarning volume exceeds the specified percentage of the (percentage) volume size. Applicable only to a thin-provisioned volume. Boolean If TRUE, the volume is thinly provisioned. ThinlyProvisioned String The DynamicStoragePool (DSP) the snapshot SnapDSPName data (SD) are provisioned from.
CIM API Programming Reference 8 InForm OS Version 2.3.1 TPD_SnapshotAdminSpaceAlert – specifies that a storage volume has failed to allocate snapshot space for administration data. 9 TPD_SnapshotUserSpaceAlert – specifies that a storage volume has failed to allocate snapshot space for user data. 5.10 Copy Services Subprofile 5.10.1 Description The subprofile defines a management interface for local snapshot management and clone management.
CIM API Programming Reference Figure 5-2. Virtual Copy Class Diagram for a Legacy Volume Copy Services Subprofile 5.
CIM API Programming Reference InForm OS Version 2.3.1 Figure 5-3. Physical Copy Class Diagram for a Legacy Volume Figure 5-4. Job Control Class Diagram 5.
CIM API Programming Reference 5.10.2.1 TPD_AffectedJobElement Association between TPD_ConcreteJob and the replica TPD_StorageVolume. Please refer to TPD_ConcreteJob on page 5.59 for a more detailed discussion. 5.10.2.2 TPD_AllocatedFromStoragePool Virtual copy snapshot volume is associated to the TPD_DeltaReplicaStoragePool via TPD_AllocatedFromStoragePool. SpaceConsumed property in this case is the space consumed by the snapshots.
CIM API Programming Reference InForm OS Version 2.3.1 5.10.2.8 TPD_DeltaReplicaStoragePool This StoragePool class is instantiated upon allocation of SA and SD space of a volume. The SA and SD spaces are modeled as TPD_DeltaReplicaStoragePool from which virtual copy snapshots (delta replica) can be allocated and created. This class is a subclass of CIM_StoragePool. CIM_StoragePool.GetSupportedSizeRange() method, which is supported in TPD_StoragePool, is not supported for TPD_DeltaReplicaStoragePool. 5.
CIM API Programming Reference 5.10.2.15 TPD_StorageConfigurationCapabilities Relevant properties are: SupportedAsynchronousActions[] – This property has been deprecated and replaced by StorageReplicationCapabilities.SupportedAsynchronousActions[], but SMI-S decrees that a provider must still specify the values here for backward compatibility with 1.0 clients. 1.1 clients ignore these values and consult those from TPD_StorageReplicationCapabilities instead.
CIM API Programming Reference a InForm OS Version 2.3.
CIM API Programming Reference 4 SupportedSpecializedElements[] - Enumeration indicating which specialized storage element types are supported by this instance of StorageReplicationCapabilities. Example values are “Delta Pool”, “Delta Snapshot”, “Full Snapshots”. This affects the value of IntendedUsage property of StorageSetting, e.g.
CIM API Programming Reference 8 InForm OS Version 2.3.1 HostAccessibleState[] - lists the replica synchronization states in which the provider allows host access to replicas. For physical copy, this is an empty array, as hosts are never allowed to access it. For virtual copy volumes, there are no restrictions whatsoever, so this array contains all the valid states that a virtual copy can have: 9 a Restore In Progress – a virtual copy promotion is ongoing. b Idle – normal state.
CIM API Programming Reference 14 DeltaReplicaPoolAccess - Indicates that a specialized pool is required as a container for delta replica elements. In our case, delta replica (virtual copy snapshots) always requires a specialized pool, the TPD_DeltaReplicaStoragePool, which corresponds to the SA/ SD space of the base volume. Possible values are: a Any – specialized pool not required for delta replicas. This is not the case for our snapshots.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-31.
CIM API Programming Reference 2 CopyType – the kind of association between source volume and replica; values are: a Sync – create and maintain a synchronous mirror copy of the source, e.g. synchronized remote copy. b c Async – create and maintain an async mirror copy of the source e.g., async remote copy. UnSyncAssoc – create and maintain an un-synchronized copy associated to the source, e.g. virtual copy or physical copy with ‘Save snapshot for later resync’ option turned on.
CIM API Programming Reference InForm OS Version 2.3.1 5.10.3.2 Associations 5.10.3.2.1 TPD_ReplicaPoolForStorage The TPD_DeltaReplicaStoragePool is associated to the source StorageVolume via TPD_ReplicaPoolForStorage. 5.10.3.2.2 TPD_AllocatedFromStoragePool New instances of TPD_AllocatedFromStoragePool are created that associate the TPD_DeltaReplicaStoragePool to: the parent StoragePool. For non-CPVV, the parent pool is a concrete pool, and whether this is “all-FC”, “all-NL”, or “all-SSD” [3.1.
CIM API Programming Reference SpaceConsumed of the TPD_AllocatedFromStoragePool between the concrete pool and TPD_DeltaReplicaStoragePool equals to the sum of the raw admin and raw snap user size. SpaceLimit and SpaceLimitWarningThreshold are both NULL since these properties apply only to CPVV.
CIM API Programming Reference InForm OS Version 2.3.1 pool. Space used by SA is not included in TotalManagedSpace, but is included in the TPD_AllocatedFromStoragePool.SpaceConsumed value, so to deduce the raw SA space, one can deduct Pool.TotalManagedSpace from SpaceConsumed. The UpdateDeltaSnapshotSpace() method should be called to prevent the value of RemainingManagedSpace from getting too stale Pool.TotalManagedSpace = raw SD size Pool.
CIM API Programming Reference SnapshotVolume: Array of references to the snapshot volume to update. If NULL, then all snapshots are updated. Job: A Job is created as a side-effect of the execution of the method, and a reference to that Job is returned through this parameter. Table 5-32.
CIM API Programming Reference InForm OS Version 2.3.1 5.10.4 Physical Copy 5.10.4.1 StorageSynchronized A TPD_StorageSynchronized association is instantiated the moment a vv copy process is started. This associates the target volume with the source volume. The values of this instance are listed in the following table. For a CopyType of UnSyncUnAssoc, an instance of TPD_StorageSynchronized is maintained while the copy is taking place, but is relinquished once the copy is finished. Table 5-33.
CIM API Programming Reference 5.10.4.2 StorageReplicationCapabilities The ability to create a physical copy is described by the following 2 instances of TPD_StorageReplicationCapabilities (seeTPD_StorageReplicationCapabilities on page 5.62): 1 UnSyncAssoc-Full – describes the capability of our provider to create an unsynchronized full-snapshot replica that maintains an association with the source volume.
CIM API Programming Reference InForm OS Version 2.3.1 CREATION CLI EQUIVALENCE createvvcopy –p createvvcopy –p -s SMI-S METHOD A physical copy can be created by a CIM client using the TPD_StorageConfigurationService.AttachOrModifyReplica() method uint32 AttachOrModifyReplica().
CIM API Programming Reference Goal: The StorageSetting properties to be created or modified for the target StorageVolume. 3PAR does not support changing the volume characteristics during createvvcopy, so this can only be NULL. A Non-NULL value is ignored. ReplicationPipe: The NetworkPipe element that scopes the remote mirror pair. This is only for remote copy, which is not supported in Phase I, so this can only be NULL.
CIM API Programming Reference InForm OS Version 2.3.1 The method execution, if successful, always returns 0x1000, which means that job has started. A client can either monitor Job.OperationalStatus for job completion or wait for the arrival of modification of OperationalStatus for a ConcreteJob to indicate ‘Complete’ and ‘OK’ or ‘Complete’ and ‘Error’. If the operation is of CopyType UnSyncAssoc, a resync snapshot of the physical copy is created.
CIM API Programming Reference RESYNCHRONIZATION CLI EQUIVALENCE createvvcopy –r SMI-S METHOD A physical copy can be resynchronized with the source volume by a CIM client using the TPD_StorageConfigurationService.ModifySynchronization() method with the Operation parameter set to Resync(4). A target volume that is in a Broken state (copy failed) cannot be resync-ed.
CIM API Programming Reference InForm OS Version 2.3.1 Quiesce: Stops the copy engine for snapshots and the snapshot no longer consume space. Not supported. Unquiesce: Take the link out of the quiesce state. Not supported. Reset to Sync: Changes the CopyType value of a mirror replica from “Async” to “Sync”. Not supported. Reset to Async: Changes the CopyType value of a mirror replica from “Sync” to “Async”. Not supported.
CIM API Programming Reference The method execution, if successful, always returns 0x1000, which means that job has started. A client can either monitor Job.OperationalStatus for job completion or wait for the modification of OperationalStatus for a ConcreteJob to indicate ‘Complete’ and ‘OK’ or ‘Complete’ and ‘Error’. STATE TRANSITIONS Table 5-37 shows the values for SyncState and WhenSynced during various stages of physical copy resynchronization. Table 5-37.
CIM API Programming Reference InForm OS Version 2.3.1 PROMOTION CLI EQUIVALENCE promotevvcopy SMI-S METHOD A physical copy can be promoted with the source volume by a CIM client using the TPD_StorageConfigurationService.ModifySynchronization() method with the Operation parameter set to Detach (2). After the a successful Detach operation, the StorageSynchronized association between the source and target volume is relinquished and the target volume becomes an independent base volume.
CIM API Programming Reference START PHYSICAL COPY CLI EQUIVALENCE createvvcopy –p -s SMI-S METHOD Copy can be done on an existing physical copy using the TPD_StorageConfigurationService.ModifySynchronization() method with the Operation parameter set to Start Copy (12). The method execution, if successful, always returns 0x1000, which means that job has started. Please see Resynchronization on page 5.77 for possible return values.
CIM API Programming Reference InForm OS Version 2.3.1 HALT PHYSICAL COPY CLI EQUIVALENCE createvvcopy –halt SMI-S METHOD Copy can be halted using the TPD_StorageConfigurationService.ModifySynchronization() method with the Operation parameter set to Stop Copy(13). This operation is synchronous and does not require a job. The job that is produced as a sideeffect of the physical copy can also be terminated by TPD_ConcreteJob.RequestStateChange.
CIM API Programming Reference Figure 5-5. State Transition Diagram of Physical Copy Copy Services Subprofile 5.
CIM API Programming Reference InForm OS Version 2.3.1 5.10.4.3 Job Control Subprofile Indications The following job control subprofile indications are supported for the job that is started as a result of the copy operation: Modification of Job Status for a Concrete Job - copy/resync started. Modification of Operational Status for a Concrete Job to Complete and OK – copy/resync successful. Modification of Operational Status for a Concrete Job to Complete and Error – copy/resync failed.
CIM API Programming Reference Table 5-41. StorageSynchronized Property Values for a Virtual Copy Property Value SyncMaintained False Synchronization is not maintained between replica and source volume. WhenSynced NULL to start with; non-NULL upon successful completion of a copy. The point in time that the Elements were synchronized. 5.10.5.
CIM API Programming Reference InForm OS Version 2.3.1 CREATION CLI EQUIVALENCE createsv SMI-S METHOD A client can create a physical copy from the source volume by using the TPD_StorageConfigurationService.CreateReplica() method.
CIM API Programming Reference Table 5-42. Return values for CreateReplica() Operation ValueMap Values Explanation/Notes 0 Job Completed with No Error 4 Failed 5 Invalid Parameter For example: the wrong CopyType is specified STATE TRANSITIONS Table 5-43 shows the values for SyncState and WhenSynced during various stages of the virtual copy creation. Table 5-43.
CIM API Programming Reference InForm OS Version 2.3.1 PROMOTION CLI EQUIVALENCE promotesv SMI-S METHOD Virtual copy promote can be done using the TPD_StorageConfigurationService.ModifySynchronization() method with the Operation parameter set to Restore (5). The method execution, if successful, always returns 0x1000, which means that job has started. STATE TRANSITIONS Here are the values for SyncState and WhenSynced during various stages of promoting virtual copy. Table 5-44.
CIM API Programming Reference HALT SNAPSHOT PROMOTION CLI EQUIVALENCE promotesv -halt SMI-S METHOD Virtual copy promote can be halted via the Job Control method TPD_ConcreteJob.RequestStateChange() method with the RequestedState parameter set to Terminate(4). STATE TRANSITIONS Here are the values for SyncState and WhenSynced during various stages of halting virtual copy promote. Table 5-45.
CIM API Programming Reference InForm OS Version 2.3.1 STATE DIAGRAM Figure 5-6. State Transition Diagram of Virtual Copy 5.10.5.2.1 Job Control Indications The following job control subprofile indications are supported for the job that is started as a result of promote operation: Modification of Job Status for a Concrete Job – promote sv/update snapspace started. Modification of Operational Status for a Concrete Job to Complete and OK – promote sv/ update snapshot space successful.
CIM API Programming Reference 5.10.6 Job Control 5.10.6.1 Overview Only the following tasks are supported Create physical copy Resync physical copy Promote virtual copy Update snapshot space 5.10.6.2 TPD_ConcreteJob This is a new class, and each instance of this class represents a task. 5.10.6.2.1 RequestStateChange() Method This method can be used to cancel a task.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-46. Return Values for RequestStateChange() Operation ValueMap Values Explanation/Notes 1 Not supported RequestedState not supported. 4 Failed 5 Invalid Parameter 4096 Method Parameters Checked - This is the normal successful return Transition Started case, as a task may not be terminated immediately. 4098 Use of Timeout Parameter Not If TimeoutPeriod parameter is not Supported NULL. 5.10.6.2.
CIM API Programming Reference 5.10.6.2.3 Mapping Error Code to CIM_Error A CIM_Error object consists of the following properties: OwningEntity – the string “SNIA” MessageID –DRM26, Resource not available. Consult SMI-S section on “Standard Messages” for detailed information on the meaning of the DRM messages. MessageArguments[] – An array containing the dynamic content of the message. There is only one element, “Operation has failed”. Message – The formatted message.
CIM API Programming Reference InForm OS Version 2.3.1 DELETING JOB CLI EQUIVALENCE removetask DELETEINSTANCE An instance of TPD_ConcreteJob can be deleted using the intrinsic method TPD_ConcreteJob.DeleteInstance(). If not deleted, a job exists indefinitely. TPD_METHODRESULT This class is used to report the extrinsic method that triggered the job and the parameters passed to it, so that a third party client can tell what the job is and what it is doing.
CIM API Programming Reference PreCall – FALSE ReturnValue - contains string representation of the method's return value, e.g., “Failed” ReturnValueType - the type of the method return value. This is always “uint32” (9) since all replication methods that we support have a return value type of uint32. 5.10.6.3 TPD_OwningJobElement Association between TPD_StorageConfigurationService and TPD_ConcreteJob. 5.10.6.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-48. Location Subprofile CIM Classes Class Description TPD_SystemPackage The Physical Element whose Location is specified. This represents the physical aspects of the InServ storage array. TPD_SystemLocation The Location of the specified Physical Element. 5.11.2 Supported Methods Table 5-49 shows the supported methods of the Location subprofile: Table 5-49.
CIM API Programming Reference Table 5-50. Multiple Computer System Subprofile CIM Classes Class Description TPD_StorageSystem Represents the storage array as a whole. TPD_NodeSystem Represents a Controller Node on an InServ Storage System. TPD_NodePairSystem Represents a pair of Controller Nodes on an InServ Storage System. TPD_NodePairRedundancySet Members of this set are node pairs that make up the InServ Storage System cluster.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-51. Software Subprofile CIM Classes Class Description TPD_StorageSystem The storage array on which the software is installed. TPD_SoftwareIdentity Information on installed software on the specified TPD_ComputerSystem. 5.13.2 Supported Methods Table 5-52 shows the supported method of the software subprofile: Table 5-52.
CIM API Programming Reference Table 5-53. Masking and Mapping Subprofile CIM Classes Class Description TPD_AuthorizedPrivilege Represents the access permission that a StorageHardwareID is allowed on a SCSIProtocolController. TPD_StorageSystem The storage array. TPD_SCSIController Represents the SCSI view of ports as seen by SCSI initiators. TPD_iSCSIController Represents the iSCSI view of ports as seen by iSCSI initiators.
CIM API Programming Reference InForm OS Version 2.3.1 5.14.2 Supported Methods Table 5-54 - Table 5-56 shows the supported methods of the masking and mapping subprofile: Table 5-54. Methods for TPD_StorageSystem Method Description modifyInstance() Provides the ability to set owner and contact information for the StorageSystem. Table 5-55. Methods for TPD_HardwareIDManagementService Method Description CreateStorageHardwareID() Expose SCSI Logical units.
CIM API Programming Reference Table 5-56. Methods for TPD_ControllerConfigurationService (continued) Method Description ExportDefaultLUs() Expose a list of SCSI logical units (such as RAID volumes) through a “default view” SCSIProtocolController (SPC) through a list of target ports. The “default view” SPC exposes logical units to all initiators. This SPC is identified by an association to a StorageHardwareID with Name property set to the empty string.
CIM API Programming Reference InForm OS Version 2.3.1 Full path SPC, where an SPC is a collection of paths with each path containing a combination of logical unit (volume), initiator port (host port), and target port. Use ExposePaths and HidePaths methods for adding/hiding this kind of path.
CIM API Programming Reference Figure 5-7. Masking and Mapping Example 1 (Direct Attached Host) Example 1 shows that there are views from 2 FC hosts with same volumes: SPC_1: Volume_1 is exported to Server 1 via Port_WWN_1 (target port on InServ) as LUN 1 and Volume_2 as LUN 2. The host HBA is represented as Host_WWN_1. SPC_2: Volume_2 is exported to Server 2 via Port_WWN_2 (target port on InServ) as LUN 5 and Volume_2 as LUN 6. The host HBA is represented as Host_WWN_2.
CIM API Programming Reference InForm OS Version 2.3.1 Figure 5-8. Masking and Mapping Example 2 (one InServ port connecting to fabric) 5.
CIM API Programming Reference Figure 5-9. Masking and Mapping Example 3 (two InServ ports connecting to fabric). 5.14.4 ProtocolControllerMaskingCapabilities This class describes the capabilities of the SPC in an InServ storage system, which describes the kind of controller configuration and StorageHardwareID management services that are available to clients. The following settings are fixed and cannot be modified: PortsPerView: Release 2.2.4 and before: 2; one port per view. Release 2.3.
CIM API Programming Reference InForm OS Version 2.3.1 OneHardwareIDPerView: Release 2.2.4 and before: true; only one StorageHardwareID (host HBA WWN/ iSCSIName) per SPC. Release 2.3.1: false. UniqueUnitNumbersPerPort: false. PrivilegeDeniedSupported: false. ProtocolControllerRequiresAuthorizedIdentity: false; CreateProtocolControllerWithPorts method is not supported.
CIM API Programming Reference 5.14.5 ControllerConfigurationService ControllerConfigurationService (CCS) is the main class of Masking and Mapping (MM) subprofile. This class enables clients to export and delete VLUNs. A client can get a handle of CCS by using a HostedService association from ComputerSystem (StorageSystem). Table 5-57 provides a brief summary of the CSS methods and their corresponding CLI commands: Table 5-57.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-57. CCS Methods and CLI Command Equivalents (continued) Methods CLI Equivalences HideDefaultLUs removevlun vvname Comments lunID n:s:p ExposeLUsToStorageHard createvlun vvname lunID wareIDCollection hostname HideLUsFromStorageHard removevlun vvname wareIDCollection lunID hostname 5.14.5.1 ExposePaths (Creating Matched-Set VLUNs) ControllerConfigurationService.ExposePaths() performs VLUN export in one method call.
CIM API Programming Reference [Out] String ResultDescriptions[]); Masking and Mapping Subprofile 5.
CIM API Programming Reference InForm OS Version 2.3.1 Job: This is ignored since InServ does not support job control. LUNames[]: An array of IDs of logical unit instances. The LU instances must already exist. The members of this array must match the Name property of StorageVolume instances. InitiatorPortIDs[]: IDs of initiator ports (host HBA WWNs). If an existing StorageHardwareID instances exist, it is used.
CIM API Programming Reference ResultDescriptions[]: An array of descriptive text of the result of the operation, with each entry containing the result of each expose path operation. This parameter is a vendorspecific extension for 3PAR. Table 5-58. ExposePath Use Cases Use Cases LUNames InitiatorPortIDs TargetPortIDs DeviceNumbers DeviceAccesses ProtocolControllers (On input) Create a new view Mandatory Mandatory Mandatory Mandatory for 2.2.4 and prior, Optional for 2.3.1 and above.
CIM API Programming Reference InForm OS Version 2.3.1 5.14.5.2 HidePaths (Removing Matched-Set VLUNs) HidePaths() is the inverse of ExposePaths. It hides a list of storage volumes from a list of initiators through a list of target ports, through one or more SCSIProtocolControllers (SPCs). This operation is similar to removevlun of matched-set VLUNs. For port-present VLUNs, see HideDefaultLUs. For host-sees VLUNs, see HideLUsFromStorageHardwareIDCollection.
CIM API Programming Reference NoVCN: Do not issue a VLUN (Virtual Logical Unit Number) Change Notification (VCN) after removal. For direct connect or loop configuration, a VCN consists of a fibre channel Loop Initialization Primitive (LIP). For fabric configuration a VCN consists of Registered State Change Notification (RSCN) being sent to the fabric controller. This parameter is a vendorspecific extension for 3PAR. The default value is false.
CIM API Programming Reference InForm OS Version 2.3.1 Remove initiatorID from a view: Remove an initiator port from a view, valid only if several host paths are zoned with a single target port. 5.14.5.3 ExposeDefaultLUs (Creating Port-Present VLUNs) ControllerConfigurationService.ExposeDefaultLUs() is similar to ExposePaths, except ExportDefaultLUs works with ‘default SPCs’, and exposes volumes to all initiators through a list of target ports through the ‘default view’ SPC.
CIM API Programming Reference elements specified in the other parameters. This is mandatory only because SMI-S requires it. For InServ, access permissions cannot be specified when creating a VLUN. Rather, each volume has its own access permission. So the 3PAR ControllerConfigurationService provider checks the passed in DeviceAccesses value against the permission of the specified LU (volume), and the operation fails if the two values do not match.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-60. ExposeDefaultLUs Use Cases ProtocolCon Use LUNames TargetPortIDs DeviceNumbers DeviceAccesses trollers (On input) Cases Create a Mandatory Mandatory Mandatory for new 2.2.4 and default before, optional view for 2.3.1 and Mandatory NULL Mandatory Contains a beyond. Add LUs Mandatory NULL Mandatory to a single view [ default SPC (Not ref support ed in 2.3.1) Parameters “Override” and “NoVCN” are optional.
CIM API Programming Reference This operation is similar to removevlun of port-present VLUNs. For matched-set VLUNs, see HidePaths. For host-sees VLUNs, see HideLUsFromStorageHardwareIDCollection.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-61. HideDefaultLUs Use Cases Use Cases LUNames TagetPortIDs ProtocolControllers (On input) Remove LUs from Mandatory NULL a view. Contains a single default SPC ref. Parameters “DeviceNumbers” and “NoVCN” are optional. All other combinations of the parameters are rejected. The use cases are: Remove volumes from a view: the volume has been exported to an SPC, it’ll be removed from the SPC (e.g.
CIM API Programming Reference [In] boolean Override, [In] boolean NoVCN, [Out] String ResultDescriptions[]); Job: This is ignored since InServ does not support job control. LUNames[]: An array of IDs of logical unit instances. The LU instances must already exist. The members of this array must match the Name property of StorageVolume instances. HostNames[]: An array of names for the hosts (StorageHardwareIDCollection). Instances MUST already exist.
CIM API Programming Reference InForm OS Version 2.3.1 NoVCN: Do not issue a VLUN (Virtual Logical Unit Number) Change Notification (VCN) after export. For direct connect or loop configuration, a VCN consists of a fibre channel Loop Initialization Primitive (LIP). For fabric configuration a VCN consists of Registered State Change Notification (RSCN) being sent to the fabric controller. This parameter is a vendorspecific extension for 3PAR. The default value is false.
CIM API Programming Reference 2 Add LUs to a view: add volumes to an existing SPC view. (this feature is not supported in 2.3.1.) 5.15 HideLUsFromStorageHardwareIDCollection (Removing Host-Sees VLUNs) HideLUsFromStorageHardwareIDCollection()is a 3PAR proprietary method that is similar to HidePaths, except that it hides volumes from all host HBA initiator ports on the specified hosts. This operation is similar to removevlun of host-sees VLUNs. For matched-set VLUNs, see HidePaths.
CIM API Programming Reference InForm OS Version 2.3.1 ResultDescriptions[]: An array of descriptive text of the result of the operation, with each entry containing the result of each hide path operation. This parameter is a vendor-specific extension for 3PAR. Table 5-63. HideLUsFromStorageHardwareIDCollection Use Cases Use Cases LUNames ProtocolControllers (On input) Remove LUs from a view Mandatory Contains a single SPC ref Parameters “DeviceNumbers” and “NoVCN” are optional.
CIM API Programming Reference Table 5-64. StorageHardwareIDManagementService Methods and CLI Equivalents Methods CLI Equivalence Comments CreateStorageHardwareID createhost Only 1 host HBA hostname WWN WWN/iscsiName (StorageID) can be specified at a time for CreateStorage HardwareID method. DeleteStorageHardwareID removehost Only 1 host HBA hostname WWN WWN/iscsiName (StorageID) can be deleted at a time for DeleteStorage HardwareID method.
CIM API Programming Reference InForm OS Version 2.3.1 The method signature is described below: uint32 CreateStorageHardwareID ( [In] String ElementName, [In] String StorageID, [In] Uint16 IDType, [In] String OtherIDType, [In] CIM_StorageClientSettingData REF Setting, [Out] CIM_StorageHardwareID REF HardwareID); ElementName: This is the name of the host to create the host HBA WWN on. The host must not have existed. This corresponds to the ElementName property of the StorageHardwareID instance.
CIM API Programming Reference [In] CIM_StorageHardwareID REF HardwareID); HardwareID: Reference to the new StorageHardwareID instance to delete. This is mandatory. 5.15.0.4 CreateStorageHardwareIDCollection (Creating a Host) This method creates a StorageHardwareIDCollection (host) and optionally a list of WWNs/iscsiNames to assign to it. This is useful to define a set of authorized subjects that can access volumes.
CIM API Programming Reference InForm OS Version 2.3.1 5.15.0.5 AddStorageHardwareIDsToCollection (Adding a Path to a Host) This method adds a list of WWNs (StorageHardwareID) to the host (StorageHardwareIDCollection). This creates the MemberOfCollection instances between the specified Collection and the StorageHardwareIDs. This operation is similar to “createhost -add “ or “createhost –add –iscsi ”. The host as specified in must have existed.
CIM API Programming Reference SAPAvailableForElement represents a one-to-one relationship between SPC and SCSIProtocolEndPoint because only one host can connect to one target port. When one InServ port is connected to a switch in a fabric, there can be multiple hosts connecting to InServ via the same target port (1-to-many association). When more than one InServ port are connecting to the fabric with multiple hosts in the same zone, this association becomes n-to-n relationship. 5.15.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-65. Properties for SCSIPrococolEndpoint Uint16 ProtocolIFType 56 (Fibre Channel) Uint16 ConnectionType 2 (Fibre Channel) Uint16 Role 2 (target port) 5.15.7 iSCSIPrococolEndpoint iSCSIPrococolEndpoint (subclass of LogicalPort) models SCSI aspects of an iSCSI port. Unlike TPD_SCSIPrococolEndpoint, however, this class is not associated to any CIM_LogicalPort class since one does not exist for iSCSI port.
CIM API Programming Reference Table 5-67. Property Values for TPD_ControllerForUnit Properties Values TPD_SCSIController Antecedent Reference to a TPD_SCSIController instance. TPD_StorageVolume Dependent Reference to an exported TPD_StorageVolume instance that is visible to protocol controller above. string DeviceNumber LUN of the storage volume via the above protocol controller. Uint16 DeviceAccess This value has to match that of StorageVolume. Figure 5-10.
CIM API Programming Reference InForm OS Version 2.3.1 5.15.10 StorageClientSettingData An array has several fixed instances of this class, each corresponding to a host persona. Each instance of StorageHardwareID and StorageHardwareIDCollection has an ElementSettingData association with an instance of StorageClientSettingData that corresponds to the persona of the host. To change the StorageClientSettingData of a host, a client should do a ModifyInstance of the TPD_StorageHardwareIDCollection.
CIM API Programming Reference 5.15.13.2 AuthorizedSubject AuthorizedSubject associates StorageHardwareID to its access permission (AuthorizedPrivilege). 5.15.13.3 AuthorizedTarget AuthorizedTarget is an association that ties AuthorizedPrivilege with SCSIProtocolController. 5.15.13.4 ConcreteDependency ConcreteDependency links the SCSIProtocolController to ControllerConfigurationService. 5.15.13.
CIM API Programming Reference InForm OS Version 2.3.1 5.16 FC Target Ports Subprofile The FC Target Ports subprofile models Fibre Channel specific aspects of a target storage system. This subprofile provides information about FC ports on an InServ Storage Server that are connected to hosts or FC switches. For detailed information regarding the FC Target Ports subprofile, refer to SMI-S at http:// www.snia.org. 5.16.
CIM API Programming Reference 5.17.1 FC Initiator Ports Subprofile CIM Classes Table 5-70 describes the FC Initiator Ports subprofile key CIM classes: d Table 5-70. FC Initiator Ports Subprofile CIM Classes Class Description TPD_StorageSystem The storage array on which the initiator ports reside. TPD_SCSIProtocolFCEndpoint A SCSI transport endpoint. In this context, this represents an initiator port on the InServ Storage System. TPD_FCPort A Fibre Channel Port residing on the TPD_StorageSystem.
CIM API Programming Reference InForm OS Version 2.3.1 The 3PAR CIM Server supports the Multiple Computer System subprofile as defined in SMI-S v1.1.0. This subprofile provides information about the Controller Nodes that comprise the InServ Storage Server cluster. The cluster is modeled as multiple tiers with each tier representing a pair of Controller Nodes. 5.18.1 iSCSI Target Ports Subprofile CIM Classes Table 5-72 describes the iSCSI Target Ports subprofile key CIM classes: Table 5-72.
CIM API Programming Reference 5.18.2 Supported Methods Table 5-73 describes the supported methods of the iSCSI target ports subprofile: Table 5-73. Methods for TPD_StorageSystem Method Description modifyInstance() Provides the ability to set owner and contact information for the StorageSystem. 5.19 Disk Drive Lite Subprofile The Disk Drive Lite subprofile models information for disk drive devices.
CIM API Programming Reference InForm OS Version 2.3.1 Table 5-74. Disk Drive Lite Subprofile CIM Classes (continued) Class Description TPD_DiskStorageExtent Provides capacity information for disk drives. TPD_StoragePool Identifies which Storage Pool contains the storage provided by specific disk drives. TPD_VolumeBasedOnDiskExtent Associations between a StorageVolume and the DiskStorageExtent that makes up the volume. Includes support for TPVV.
CIM API Programming Reference 5.20 Block Server Performance Subprofile The Block Server Performance Subprofile defines classes and methods for managing performance information (statistics) in block servers. For detailed information regarding the Block Server Performance subprofile, refer to SMI-S at http://www.snia.org. 5.20.1 Block Server Performance Subprofile CIM Classes Table 5-76 describes the various block server performance subprofile key CIM classes: Table 5-76.
CIM API Programming Reference 5.138 Block Server Performance Subprofile InForm OS Version 2.3.
InForm OS Version 2.3.1 CIM API Programming Reference 6 CIM Indications In this chapter 6.1 Overview 6.1 6.2 Fibre Channel Ports 6.1 6.1 Overview SMI-S provides for asynchronous notification of events that indicate changes in the CIM server or the managed elements controlled by the CIM server. CIM Indications are the mechanism for delivery of such events. A CIM client must subscribe to indications it wants to receive event notifications from the CIM server.
CIM API Programming Reference InForm OS Version 2.3.1 6.3 Job Control for Copy Services The 3PAR CIM Server supports indication subscriptions for changes in the operational status of a concrete job related to Copy Services. Clients must send the following query string to the 3PAR CIM Server: SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_ConcreteJob 6.4 Thin Provisioning The 3PAR CIM Server supports indication subscriptions for various thin provisioning related alert indications.
InForm OS Version 2.3.1 CIM API Programming Reference 7 3PAR CIM-API Extensions In this chapter 7.1 Health Management 7.2 7.1.1 Controller Node Subsystem 7.2 7.1.2 Supported Methods 7.5 7.1.3 Disk Enclosure Subsystem 7.6 7.1.4 Supported Methods 7.9 7.1.5 Power and Cooling 7.10 7.1.6 Supported Methods 7.14 7.2 Inventory Management 7.15 7.2.1 Controller Node Subsystem 7.15 7.2.2 Supported Methods 7.19 7.2.3 Disk Enclosure Subsystem 7.20 7.2.4 Supported Methods 7.24 7.2.
CIM API Programming Reference InForm OS Version 2.3.1 The 3PAR CIM Server supports additional classes that provide management for InServ Storage Server specific features not covered by SMI-S. 7.1 Health Management The 3PAR CIM Server provides the ability to retrieve health information about the physical devices that comprise the InServ Storage Server. This can be broken down into the following areas: The Controller Node Subsystem The Disk Enclosure Subsystem Power and Cooling 7.1.
InForm OS Version 2.3.1 CIM API Programming Reference Table 7-1. Controller Node Subsystem CIM Classes (continued) Class Description TPD_NodeCPU Provides information about the CPU(s) contained within each Controller Node. TPD_PhysicalMemory Provides information about the physical memory contained within each Controller Node. TPD_IDEDrive Provides information about the onboard IDE drive contained within each Controller Node. 7.1.1.2 Properties for TPD_StorageSystem Table 7-2.
CIM API Programming Reference InForm OS Version 2.3.1 Table 7-3. TPD_NodeSystem Properties (continued) Property Description OperationalStatus Overall status of the controller node. Refer to SMI-S for possible values of this property. OtherOperationalStatus 3PAR specific operational status for the NodeSystem. 7.1.1.4 Properties for TPD_PCICard Table 7-4. TPD_PCICard Properties Property Description Slot Slot number in which this card is inserted.
InForm OS Version 2.3.1 CIM API Programming Reference 7.1.1.6 Properties for TPD_PhysicalMemory Table 7-6. TPD_PhysicalMemory Properties Property Description Slot Slot number in which this memory card is inserted. SlotID Connector ID where this card is inserted (such as J1101). OperationalStatus Overall status of the memory card. Refer to SMI-S for possible values of this property. OtherOperationalStatus 3PAR specific operational status for the memory card. 7.1.1.
CIM API Programming Reference InForm OS Version 2.3.1 7.1.2.1 UML Diagram Figure 7-1. Controller Node Subsystem 7.1.3 Disk Enclosure Subsystem The 3PAR CIM Server provides the ability to manage the health of physical devices that comprise the backend Disk Enclosure portion of the InServ Storage Server. 7.1.3.1 Disk Enclosure Subsystem CIM Classes Table 7-9 shows the key classes of the Disk Enclosure Subsystem: Table 7-9.
InForm OS Version 2.3.1 CIM API Programming Reference Table 7-9. Disk Enclosure Subsystem (continued) Class Description TPD_Magazine Provides information about drive magazines contained within a TPD_DriveCage. TPD_DiskDrive Provides information about disk drives. TPD_DiskDrivePackage Physical aspects of a disk drive. This class is used to gather information about the association of drive magazines to disk drives. 7.1.3.2 Properties for TPD_StorageSystem Table 7-10.
CIM API Programming Reference InForm OS Version 2.3.1 Table 7-11. TPD_DriveCage Properties (continued) Property Description OperationalStatus Overall status of the drive cage. Refer to SMI-S for possible values for this property. OtherOperationalStatus 3PAR specific operational status for the DriveCage. 7.1.3.4 Properties for TPD_CageInterfaceCard Table 7-12. TPD_CageInterfaceCard Properties Property Description Position The position of the CageInterfaceCard in the DriveCage.
InForm OS Version 2.3.1 CIM API Programming Reference 7.1.3.6 Properties for TPD_DiskDrive Table 7-14. TPD_DiskDrive Properties Property Description ElementName User-friendly name of the disk drive. The format varies depending on the type of the drive cage. Name The Fibre Channel WWN of this disk drive. Position The position of this disk drive in the drive magazine. ID ID assigned to this Disk Drive by the system. OperationalStatus Overall status of the disk drive.
CIM API Programming Reference InForm OS Version 2.3.1 7.1.4.1 UML Diagram Figure 7-2. Disk Enclosure Subsystem 7.1.5 Power and Cooling The 3PAR CIM Server provides information about the devices used to power and cool the InServ Storage Server. 7.1.5.1 Power and Cooling CIM Classes Table 7-16 shows the key CIM classes: Table 7-16. Power and Cooling CIM Classes Class Description TPD_StorageSystem The storage array.
InForm OS Version 2.3.1 CIM API Programming Reference Table 7-16. Power and Cooling CIM Classes (continued) Class Description TPD_DriveCage Provides information about InServ Storage Server drive cages. TPD_PowerSupply Provides information about power supplies for both controller nodes and disk cages. TPD_Battery Provides information about batteries attached to controller node power supplies.
CIM API Programming Reference InForm OS Version 2.3.1 Table 7-18. TPD_NodeSystem Properties (continued) Property Description OperationalStatus Overall status of the Controller Node. Please refer to SMI-S for possible values of this property. OtherOperationalStatus 3PAR specific operational status for the NodeSystem. 7.1.5.4 Properties for TPD_DriveCage Table 7-19.
InForm OS Version 2.3.1 CIM API Programming Reference Table 7-20. TPD_PowerSupply Properties (continued) Property Description ACStatus Provides information about the AC status of a power supply. DCStatus Provides information about the DC status of a power supply. 7.1.5.6 Properties for TPD_Battery Table 7-21. TPD_Battery Properties Property Description Position The position of the Battery in the storage system (such as the battery number). OperationalStatus Overall status of the Battery.
CIM API Programming Reference InForm OS Version 2.3.1 7.1.6 Supported Methods Table 7-1 shows the supported methods of the StorageSystem: Table 7-23. Methods for TPD_StorageSystem Method Description modifyInstance() Provides the ability to set owner and contact information for the StorageSystem. 7.1.6.1 UML Diagram Figure 7-3. Power and Cooling 7.
InForm OS Version 2.3.1 CIM API Programming Reference 7.2 Inventory Management The 3PAR CIM Server provides the ability to retrieve inventory information for Controller Nodes and all of the components that comprise the Controller Node Subsystem portion of the InServ Storage Server. 7.2.1 Controller Node Subsystem The 3PAR CIM Server provides the ability to retrieve inventory information about the physical devices that comprise the InServ Storage Server.
CIM API Programming Reference InForm OS Version 2.3.1 Table 7-24. Controller Node Subsystem CIM Classes (continued) Class TPD_PhysicalMemory Description Provides information about the physical memory contained within each Controller Node. TPD_IDEDrive Provides information about the onboard IDE drive contained within each Controller Node. 7.2.1.2 Properties for TPD_StorageSystem Table 7-25. TPD_StorageSystem Properties Property Description Name The Node WWN for the storage system.
InForm OS Version 2.3.1 CIM API Programming Reference 7.2.1.4 Properties for TPD_NodeSystem Table 7-27. TPD_NodeSystem Properties Property Description Position The position of the Controller Node in the storage system (such as the node number). ElementName User friendly name of the Controller Node. 7.2.1.5 Properties for TPD_NodePackage Table 7-28. TPD_NodePackage Properties Property Description Manufacturer Manufacturer of the Controller Node. Model Model of the Controller Node.
CIM API Programming Reference InForm OS Version 2.3.1 7.2.1.7 Properties for TPD_NodeCPU Table 7-30. TPD_NodeCPU Properties Property Description Position The position/CPU number of this component. Manufacturer Manufacturer of the CPU. Model Model number for the CPU. SerialNumber Serial number for the CPU. 7.2.1.8 Properties for TPD_PhysicalMemory Table 7-31. TPD_PhysicalMemory Properties Property Description Slot Slot number where this memory card is inserted.
InForm OS Version 2.3.1 CIM API Programming Reference Table 7-32. TPD_IDEDrive Properties (continued) Property Description SerialNumber Serial number for the drive. FwRevision Revision of the firmware running on the drive. 7.2.2 Supported Methods Table 7-1 shows the supported method of the StorageSystem: Table 7-33. Methods for TPD_StorageSystem Method Description modifyInstance() Provides the ability to set owner and contact information for the StorageSystem. 7.2.2.1 UML Diagram Figure 7-4.
CIM API Programming Reference InForm OS Version 2.3.1 7.2.3 Disk Enclosure Subsystem The 3PAR CIM Server provides the ability to retrieve inventory information for all of the components that comprise the backend Disk Enclosure portion of the InServ Storage Server. 7.2.3.1 Disk Enclosure Subsystem CIM Classes Table 7-34 shows the Disk Enclosure Subsystem key classes: Table 7-34. Disk Enclosure Subsystem Class Description TPD_StorageSystem The storage array.
InForm OS Version 2.3.1 CIM API Programming Reference 7.2.3.3 Properties for TPD_DriveCage Table 7-36. TPD_DriveCage Properties Property Description Position The position of the drive cage in the storage system (such as the cage number). ElementName User-friendly name of the Drive Cage. Manufacturer Manufacturer of the Drive Cage. Model Model of the Drive Cage. SerialNumber Serial number of the Drive Cage. 7.2.3.4 Properties for TPD_CageInterfaceCard Table 7-37.
CIM API Programming Reference InForm OS Version 2.3.1 7.2.3.5 Properties for TPD_Magazine Table 7-38. TPD_Magazine Properties Property Description ElementName User-friendly name of the drive magazine. The format vary depending on type of drive cage. Position The position of this drive magazine in the drive cage. Manufacturer Manufacturer of the magazine. Model Model of the magazine. SerialNumber Serial number of the magazine. 7.2.3.6 Properties for TPD_DiskDrive Table 7-39.
InForm OS Version 2.3.1 CIM API Programming Reference Table 7-40. TPD_DiskDrivePackage Properties (continued) Property Description Model Model of the DiskDrive. SerialNumber Serial number of the DiskDrive. 7.2.3.8 Properties for TPD_DiskSoftwareIdentity Table 7-41. TPD_DiskSoftwareIdentity Properties Property Description Manufacturer Manufacturer of the DiskDrive firmware. VersionString Version of the firmware running on the DiskDrive. Inventory Management 7.
CIM API Programming Reference InForm OS Version 2.3.1 7.2.4 Supported Methods Table 7-1 shows the supported method of the StorageSystem : Table 7-42. Methods for TPD_StorageSystem Method Description modifyInstance() Provides the ability to set owner and contact information for the StorageSystem. 7.2.4.1 UML Diagram Figure 7-5. Disk Enclosure Subsystem 7.
InForm OS Version 2.3.1 CIM API Programming Reference 7.2.5 Power and Cooling The 3PAR CIM Server provides the ability to retrieve inventory information for the physical devices used to power and cool the InServ Storage Server. 7.2.5.1 Power and Cooling CIM Classes Table 7-43 shows the Power and Cooling key classes: Table 7-43. Power and Cooling CIM Classes Class Description TPD_StorageSystem The storage array.
CIM API Programming Reference InForm OS Version 2.3.1 7.2.5.3 Properties for TPD_NodeSystem Table 7-45. TPD_NodeSystem Properties Property Description Position The position of the Controller Node in the storage system (such as the node number). ElementName User-friendly name of the Controller Node. 7.2.5.4 Properties for TPD_DriveCage Table 7-46. TPD_DriveCage Properties Property Description Position The position of the DriveCage in the storage system (such as the cage number).
InForm OS Version 2.3.1 CIM API Programming Reference Table 7-47. TPD_PowerSupply Properties (continued) Property Description Model Model of the PowerSupply. SerialNumber Serial number of the PowerSupply. 7.2.5.6 Properties for TPD_Battery Table 7-48. TPD_Battery Properties Property Description Position The position of the Battery in the storage system (such as the battery number). Manufacturer Manufacturer of the Battery. Model Model of the Battery.
CIM API Programming Reference InForm OS Version 2.3.1 7.2.6 Supported Methods Table 7-1 shows the supported method of the StorageSystem: Table 7-50. Methods for TPD_StorageSystem Method Description modifyInstance() Provides the ability to set owner and contact information for the StorageSystem. 7.2.6.1 UML Diagram Figure 7-6. Power and Cooling 7.
InForm OS Version 2.3.1 CIM API Programming Reference A Managed Object Format Files In this appendix 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.90 A.6 3PAR_TPDEnv.mof A.101 A.7 3PAR_TPDLocation.mof A.109 A.8 3PAR_TPDEthPort.mof A.110 A.9 3PAR_TPDiSCSI.mof A.113 A.10 3PAR_TPDStats.mof A.124 This appendix provides the contents of the Managed Object Format (MOF) files for the InServ Storage Server.
CIM API Programming Reference InForm OS Version 2.3.1 NOTE: The MOF's in this chapter might not be current; for the up-to-date MOFs, please copy and paste from the files in the /net/toolchest/export/bk/swiss_2.3.1/ tpdsrc/umod/api/pegasus/Schemas/TPD directory. A.1 3PAR_InterOp.mof This MOF contains 3PAR classes that loaded into the root/PG_InterOp namespace.
InForm OS Version 2.3.1 CIM API Programming Reference [Override ( "Antecedent" ), Min ( 1 ), Description ( "The RegisteredProfile that is referenced/required by the " "subprofile.")] TPD_RegisteredProfile REF Antecedent; [Override ( "Dependent" ), Description ( "A RegisteredSubProfile that requires a scoping profile, for " "context.
CIM API Programming Reference InForm OS Version 2.3.1 Description ( "TPD_HostedOMService is an association between TPD_ObjectManager and the " "System on which the functionality resides. The cardinality of " "this association is 1-to-many. A System may host many " "Services. Services are weak with respect to their hosting " "System. Heuristic: A Service is hosted on the System where the " "LogicalDevices or SoftwareFeatures that implement the Service " "are located.
InForm OS Version 2.3.1 CIM API Programming Reference TPD_ObjectManager REF Antecedent; [Override ( "Dependent" ), Weak, Description ( "The Namespace in an ObjectManager.
CIM API Programming Reference InForm OS Version 2.3.1 [Override ( "Antecedent" ), Min ( 1 ), Max ( 1 ), Description ( "The 3PAR CIM server ObjectManager whose communication mechanism is " "described.")] TPD_ObjectManager REF Antecedent; [Override ( "Dependent" ), Min ( 1 ), Description ( "The encoding/protocol/set of operations that may be used to " "communicate with the referenced ObjectManager.
InForm OS Version 2.3.
CIM API Programming Reference InForm OS Version 2.3.1 "to primordial pool."), ValueMap {"0", "1", "2"}, Values {"Unknown", "FC", "Nearline"} ] uint16 DiskDeviceType; }; // ================================================================== // 3PAR StorageVolume // ================================================================== [Description ( "3PAR Data StorageVolume ")] class TPD_StorageVolume: CIM_StorageVolume { [Description ( "Describe the RAID type of the volume.
InForm OS Version 2.3.1 CIM API Programming Reference "can be calculated by multiplying BlockSize by RawAdminBlocks.")] uint64 RawAdminBlocks; [Description ( "The maximum number of blocks, of size BlockSize, which are " "available for consumption in Admin space. The total size " "can be calculated by multiplying BlockSize by ConsumableAdminBlocks.")] uint64 ConsumableAdminBlocks; [Description ( "Total number of logically contiguous blocks, of size Block " "Size, which form Free Size Admin.
CIM API Programming Reference InForm OS Version 2.3.1 [Description ( "Number of free zones in the Copy space.")] uint64 FreeCopyZones; [Description ( "The date this volume was created.")] datetime DateCreated; [Description ( "Master node ID.") ] uint16 MasterNode; [Description ( "Backup 1 node ID.") ] uint16 BackupNode1; [Description ( "Backup 2 node ID.") ] uint16 BackupNode2; [Description ( "Parent volume ID.") ] uint32 ParentID; [Description ( "Volume policy bits used to store policies information.
InForm OS Version 2.3.1 CIM API Programming Reference " default setting. " "TPNoZeroFill - Bypass the zero-fill stage on allocation of partially " " written data pages. This is a performance improvement " " setting for Thin Provisioned volumes. " "OneHost - This constrains the export of a volume to one host or " " one host cluster (when cluster names may be used as a " " host name).
CIM API Programming Reference InForm OS Version 2.3.1 [Description ( "Describes the export state of the volume."), ValueMap {"0", "1", "2"}, Values {"None", "Active", "Template"} ] uint16 ExportState; [Description ( "Type of disk drives that are used to create this volume."), ValueMap {"0", "1", "2"}, Values {"Unknown", "FC", "Nearline"} ] uint16 DiskDeviceType; [Description ( "Allocation warning.
InForm OS Version 2.3.1 CIM API Programming Reference [Description ( "The DynamicStoragePool (DSP) the user space " "is provisioned from.\n")] String UserDSPName; [Description ( "The number of user blocks that are actually allocated to a " "thin-provisioned volume. " "This is applicable only for a thin-provisioned volume.")] uint64 ProvisionedConsumableBlocks; [Description ( "Name of the administrative domain that this volume belongs " "to.\n")] String Domain; [Description ( "Number of chunklets in a set.
CIM API Programming Reference InForm OS Version 2.3.1 [Association, Aggregation, Composition, Description ( "3PAR HostedStoragePool (association between StoragePool and " "StorageSystem) ")] class TPD_HostedStoragePool: CIM_HostedStoragePool { [Override ("GroupComponent"), Aggregate, Max (1), Min (1), Description ("The parent system in the association.") ] TPD_StorageSystem REF GroupComponent; [Override ("PartComponent"), Description ( "The StoragePool that is on the system.
InForm OS Version 2.3.1 CIM API Programming Reference uint16 ParitySetSize; [Write, Description ( "Base ID of the volume. If NULL, the next available " "id used."), MinValue ( 1 ) ] uint32 BaseID; [Write, Description ( "Whether a RAID 10 or RAID 50 volume supports a failure " "of one port pair, one cage or one magazine. For RAID 10 " "and RAID 50, the default for user, snap admin and snap " "data areas are cage. For RAID 0, the default for the " "snap admin area is cage.
CIM API Programming Reference InForm OS Version 2.3.1 uint64 AdminVolumeSize; [Write, Description ( "Provision snapshot data (SD) and snapshot admin (SA) " "space from the Common Provisioning Group CPGName.\n")] String CPGName; [Write, Description ( "If TRUE, the volume or pool is thinly provisioned.") ] boolean ThinlyProvisioned; [Write, Description ( "Define volume policy.
InForm OS Version 2.3.1 CIM API Programming Reference "NoZeroDetect - No need to check if incoming data is zero.
CIM API Programming Reference InForm OS Version 2.3.1 String DiskPrimPathNodes[]; [Write, Description ( "Specifies the PCI slot, the list of PCI slots or " "the range of PCI slots the disks must have their " "primary path on.\n" "Each element in this array represents one instance of " "pattern for candidate disks; multiple array element adds " "additional candidate disks that match the pattern.\n" "Empty string means that the value is not specified for " "this particular set of patterns.
InForm OS Version 2.3.1 CIM API Programming Reference "DiskPrimPathPCISlots", "DiskPrimPathNodes", "DiskCages", "DiskMagazines", "DiskMagPositions", "DiskIDs", "DiskTotalChunkletGT", "DiskTotalChunkletLT", "DiskFreeChunkletGT", "DiskFreeChunkletLT", "DiskPackageModels" }] String DiskPrimPathPorts[]; [Write, Description ( "Specifies the cage number, the list of cage numbers or " "the range of cage numbers the disks must be in.
CIM API Programming Reference InForm OS Version 2.3.1 "pattern for candidate disks; multiple array element adds " "additional candidate disks that match the pattern.\n" "Empty string means that the value is not specified for " "this particular set of patterns.
InForm OS Version 2.3.1 CIM API Programming Reference "DiskFreeChunkletGT", "DiskFreeChunkletLT", "DiskPackageModels" }] String DiskMagPositions[]; [Write, Description ( "Specifies the ID, the list of IDs or the range of IDs " "the disks must have.\n" "Each element in this array represents one instance of " "pattern for candidate disks; multiple array element adds " "additional candidate disks that match the pattern.
CIM API Programming Reference InForm OS Version 2.3.1 "DiskPrimPathNodes", "DiskMagazines", "DiskMagPositions", "DiskIDs", "DiskCages", "DiskTotalChunkletLT", "DiskFreeChunkletGT", "DiskFreeChunkletLT", "DiskPackageModels" }] sint32 DiskTotalChunkletGT[]; [Write, Description ( "The total number of chunklets in the disk must be " "less than this value.
InForm OS Version 2.3.1 CIM API Programming Reference ModelCorrespondence { "DiskPrimPathPCISlots", "DiskPrimPathPorts", "DiskPrimPathNodes", "DiskMagazines", "DiskMagPositions", "DiskIDs", "DiskTotalChunkletGT", "DiskTotalChunkletLT", "DiskCages", "DiskFreeChunkletLT", "DiskPackageModels" }] sint32 DiskFreeChunkletGT[]; [Write, Description ( "The total number of free or initializing chunklets in " "the disk must be less than this value.
CIM API Programming Reference InForm OS Version 2.3.1 "this particular set of patterns. \n" "The string must be in one of the following formats:\n" " - the disk drive model\n" " , - a list of disk drive models\n"), ArrayType ( "Indexed" ), ModelCorrespondence { "TPD_DiskDrivePackage.
InForm OS Version 2.3.1 CIM API Programming Reference "The setting data used when volume is allocated")] TPD_StorageSetting REF SettingData; }; // ================================================================== // 3PAR StorageConfigurationService // ================================================================== [Description ("The StorageConfigurationService provides methods that allow " "a client to create, modify and delete storage pools and " "volumes.
CIM API Programming Reference InForm OS Version 2.3.1 "Unknown", "Timeout", "Failed", "Invalid Parameter", "In Use", "DMTF Reserved", "Method Parameters Checked - Job Started", "Size Not Supported", "Method Reserved", "Vendor Specific" }] uint32 CreateOrModifyStoragePool ( [IN, Description ( "A end user relevant name for the pool being created. If " "NULL, then a system supplied default name can be used. " "The value stored in the 'ElementName' property " "for the created pool.
InForm OS Version 2.3.1 CIM API Programming Reference "For 3PAR provider, this can only contain string reference " "to the primordial pool, as creation of pool from another " "pool is not supported.")] string InPools[], [IN, Description ( "Array of strings containing representations of " "references to CIM_StorageExtent instances, that are used " "to create the Pool or modify the source extents. " "For 3PAR provider, if this is NULL, then all available " "extents in the system used to create the pool.
CIM API Programming Reference InForm OS Version 2.3.1 [Override ( "ManagedElement" ), Description ( "The StorageConfigurationService.")] TPD_StorageConfigurationService REF ManagedElement; [Override ( "Capabilities" ), Description ( "The features supported by StorageConfigurationService.")] TPD_StorageConfigurationCapabilities REF Capabilities; }; // ================================================================== // 3PAR System and ControllerConfigurationService association.
InForm OS Version 2.3.1 CIM API Programming Reference "Fabric"} ] uint16 Topology; [Description ("Daisy chain configuration of the port"), ValueMap {"0", "1", "2"}, Values {"Unknown", "Valid", "Invalid"} ] uint16 Configuration; [Description ("Mode of the port"), ValueMap {"0", "1", "2"}, Values {"Suspended", "Target", "Initiator"} ] uint16 Mode; [Description ("Shows if the mode change is allowed or not.")] boolean ModeChangeAllowed; [Description ("Node WWN of the port.
CIM API Programming Reference InForm OS Version 2.3.1 [Description ("Interrupt coalescing support."), ValueMap {"0", "1", "2"}, Values {"Unknown", "Enable", "Disable"} ] uint16 InterruptCoalescing; // ========================================= // Operations // ========================================= [Description ( "This method sets port Offline." "The method should return 0 if successful, 1 if the request is not " "supported, and some other value if any other error occurred.
InForm OS Version 2.3.1 CIM API Programming Reference Values {"OK", "Not Supported", "Error"} ] uint32 InitializeLoop( [IN, Description ( "Name of the cage to issue LIP through."), ModelCorrespondence { "TPD_DriveCage.ElementName" }] string CageName ); [Description ( "Verify current port database with Name Server when fabric attached. " "Devices in database but not in Name Server removed. " "If RSCN messages are suppressed or lost in the fabric then such " "devices shown until removed with this command.
CIM API Programming Reference InForm OS Version 2.3.1 " association. ")] class TPD_ControllerForPort : CIM_ProtocolControllerForPort { [Override ("Antecedent"), Description ("The SCSI Protocol Controller.") ] TPD_SCSIController REF Antecedent; [Override ("Dependent"), Weak, Description ( "The FCPort controlled by the SCSI protocol controller.
InForm OS Version 2.3.1 CIM API Programming Reference // 3PAR SCSIProtocolEndpoint on FC-AL card (connects to initiator // endpoint on the node controller) // ================================================================== //[Description // ("3PAR Data InServ SCSIProtocolEndpoint that resides on the " // "FC-AL card. This endpoint is connected to the initiator FC " // "endpoint the node controller.
CIM API Programming Reference InForm OS Version 2.3.1 // CIM_FCPort REF Antecedent; -- reenable this line if we support TPD_SCSIInitTargetLUPath [Override ( "Dependent" ), Description ( "The SCSIProtocolEndpoint implemented using the FC port.
InForm OS Version 2.3.1 CIM API Programming Reference "paths to the existing SPC. \n" "\n" "For creating an SPC, all parameters, except ProtocolControllers, " "MUST be specified since SPCAllowsNoLUs, SPCAllowsNoTargets and " "SPCAllowsNoInitiators properties are all false, and " "ClientSelectableDeviceNumbers property is true, for a 3PAR " "InServ array.
CIM API Programming Reference InForm OS Version 2.3.1 "Invalid logical unit ID", "Invalid initiator port ID", "Invalid target port ID", "Invalid permission", "Target/initiator combination already exposed", "Requested logical unit number in use", "Maximum Map Count Exceeded", "Method Reserved", "Vendor Specific" }] uint32 ExposePaths ( [IN ( false ), OUT, Description ( "Reference to the job if 'Method Parameters Checked - Job " "Started' is returned (MAY be null if job completed).
InForm OS Version 2.3.1 CIM API Programming Reference "A list of permissions to assign to the corresponding " "logical unit in the LUNames parameter. This specifies " "the permission to assign within the context of the " "elements specified in the other parameters. Setting this " "to 'No Access' assigns the DeviceNumber for the " "associated initiators, but does not grant read or write " "access. If the LUNames parameter is not null then this " "parameter MUST be specified.
CIM API Programming Reference InForm OS Version 2.3.1 "Notification (RSCN) being sent to the fabric controller. " "This parameter is a vendor-specific extension for 3PAR. " "The default value is false.")] boolean NoVCN, [OUT, Description ( "An array of descriptive text of the result of the operation, " "with each entry containing the result of each " "expose path operation.
InForm OS Version 2.3.1 CIM API Programming Reference "\n" "The SPC is automatically deleted when the last logical unit " "is removed since SPCAllowsNoLUs is false."), ValueMap { "0", "1", "2", "3", "4", "5", "6..4095", "4096", "4097", "4098", "4099", "4100", "4101..32767", "32768..
CIM API Programming Reference InForm OS Version 2.3.1 "but its use enhance efficiency of the HidePaths " "operation."), ModelCorrespondence { "CIM_ProtocolControllerForUnit.DeviceNumber"}] string DeviceNumbers[], [IN, OUT, Description ( "An array of references to SCSIProtocolControllers " "(SPCs). On input, this MUST contain exactly one element; " "there MAY be multiple references on output.
InForm OS Version 2.3.1 CIM API Programming Reference "initiators. This SPC is identified by an association to a " "StorageHardwareID with Name property set to the empty " "string. \n" "\n" "The parameters for this method are: Job - null if no job " "created, otherwise this is a reference to the job. LUNames " "- the list of names of the logical units to use. " "TargetPortIDs - the names of the target ports to use. " "DeviceNumbers - the device numbers (LUNs) to use.
CIM API Programming Reference InForm OS Version 2.3.1 "provided by SCSI REPORT LUNS and INQUIRY commands) \n" "- each LogicalDevice associated to an SPC MUST have a " "unique ProtocolControllerForUnit DeviceNumber (logical unit " "number) \n" "The instrumentation MUST report an error if the client " "request would violate one of these rules.
InForm OS Version 2.3.1 CIM API Programming Reference "then this parameter MUST be null. Otherwise, if this " "parameter is null, all LU numbers are assigned by the " "hardware or instrumentation."), ModelCorrespondence { "CIM_ProtocolControllerForUnit.DeviceNumber"}] string DeviceNumbers[], [IN, Description ( "A list of permissions to assign to the corresponding " "logical unit in the LUNames parameter.
CIM API Programming Reference InForm OS Version 2.3.1 boolean Override, [IN, Description ( "Do not issue a VLUN (Virtual Logical Unit Number) Change " "Notification (VCN) after export. For direct connect or " "loop configuration, a VCN consists of a Fibre Channel " "Loop Initialization Primitive (LIP). For fabric " "configuration a VCN consists of Registered State Change " "Notification (RSCN) being sent to the fabric controller. " "This parameter is a vendor-specific extension for 3PAR.
InForm OS Version 2.3.1 CIM API Programming Reference "\n" "When hiding logical units, 3PAR InServ array supports only " "the Remove LUs from a default view use case. " "Remove LUs from a default view requires that the " "LUNames parameter not be null and that the TargetPortIDs " "parameters be null. \n" "\n" "The SPC is automatically deleted when the last logical unit " "is removed since SPCAllowsNoLUs is false."), ValueMap { "0", "1", "2", "3", "4", "5", "6..4095", "4096", "4097", "4098", "4099", "4100.
CIM API Programming Reference InForm OS Version 2.3.1 ModelCorrespondence { "CIM_ProtocolControllerForUnit.DeviceNumber" }] string DeviceNumbers[], [IN, OUT, Description ( "An array of references to SCSIProtocolControllers " "(SPCs). On input, this MUST contain exactly one element; " "there MAY be multiple references on output. The " "instrumentation attempt to remove associations " "(LUNames or TargetPortIDs) from this SPC.
InForm OS Version 2.3.1 CIM API Programming Reference "DeviceNumbers - the device numbers (LUNs) to use. " "DeviceAccesses - permissions for the logical units. " "ProtocolControllers - SPCs involved in this operation. \n" "\n" "There are two modes of operation, create and modify. If a " "NULL value is passed in for the SPC, then the " "instrumentation attempt to create a new view. " "If an SPC is passed in, then the instrumentation adds the " "new paths to the existing SPC.
CIM API Programming Reference InForm OS Version 2.3.1 "host/target port pair that is in use by another SPC.
InForm OS Version 2.3.1 CIM API Programming Reference ModelCorrespondence { "TPD_StorageHardwareIDCollection.ElementName" }] string HostNames[], [IN, Description ( "A list of logical unit numbers to assign to the " "corresponding logical unit in the LUNames parameter. " "(within the context of the elements specified in the " "other parameters). If the LUNames parameter is null, " "then this parameter MUST be null.
CIM API Programming Reference InForm OS Version 2.3.1 "SPCs created or modified as the result of processing the " "request.")] CIM_SCSIProtocolController REF ProtocolControllers[], [IN, Description ( "Override existing lower priority VLUNs, if necessary. " "Can be used only when exporting to a specific host. " "This parameter is a vendor-specific extension for 3PAR. " "The default value is false.
InForm OS Version 2.3.1 CIM API Programming Reference "the instrumentation MUST return a 'Invalid Parameter' " "status or a CIM_Error. \n" "\n" "When hiding logical units, 3PAR InServ array supports only " "the Remove LUs from a view use case. " "Remove LUs from a view requires that the " "LUNames parameter not be null.\n" "\n" "The SPC is automatically deleted when the last logical unit " "is removed since SPCAllowsNoLUs is false."), ValueMap { "0", "1", "2", "3", "4", "5", "6..
CIM API Programming Reference InForm OS Version 2.3.1 "An array of references to SCSIProtocolControllers " "(SPCs). On input, this MUST contain exactly one element; " "there MAY be multiple references on output. The " "instrumentation attempt to remove associations " "(LUNames or TargetPortIDs) from this SPC. Depending upon " "the specific implementation, the instrumentation MAY " "need to create new SPCs with a subset of the remaining " "associations.
InForm OS Version 2.3.1 CIM API Programming Reference // ================================================================== [Association, Description ( "TPD_SystemControllerMaskingCapabilities is an association between " "StorageSystem and ProtocolControllerMaskingCapabilities.") ] class TPD_SystemControllerMaskingCapabilities : CIM_ElementCapabilities { [Override ( "ManagedElement" ), Description ( "The StorageSystem.
CIM API Programming Reference InForm OS Version 2.3.1 Description ("The storage system.") ] TPD_StorageSystem REF GroupComponent; [Override ("PartComponent"), Weak, Description ( "The storage volume on storage system.
InForm OS Version 2.3.1 CIM API Programming Reference "3PAR system package describes InServ's system packaging attributes " " including model, serial number and OS version.
CIM API Programming Reference InForm OS Version 2.3.1 class TPD_CapabilitiesOfStoragePool: CIM_ElementCapabilities { [Override ( "ManagedElement" ), Description ( "The StoragePool.")] TPD_StoragePool REF ManagedElement; [Override ( "Capabilities" ), Description ( "The capabilities (RAID types) that the StoragePool can support.
InForm OS Version 2.3.1 CIM API Programming Reference "This association define StorageSettings that reflect the " "capabilities of the associated StorageCapabilities. The " "associated StorageSetting may not define the operational " "characteristics (through settings properties) of any storage " "element.
CIM API Programming Reference InForm OS Version 2.3.1 }; // ================================================================== // 3PAR Product and System Package association // ================================================================== [Association, Aggregation, Composition, Description ( "3PAR Data InServ Product and System Package Association.
InForm OS Version 2.3.1 CIM API Programming Reference "to its access permission (AuthorizedPrivilege).")] class TPD_PrivilegeForStorageHardwareID : CIM_AuthorizedSubject { [Override ( "Privilege" ), Description ( "The AuthorizedPrivilege either granted or denied to an " "Identity, Role or Collection. Whether the privilege is " "granted or denied is defined by the inherited property, " "CIM_Privilege.PrivilegeGranted.
CIM API Programming Reference InForm OS Version 2.3.1 // ================================================================== // MemberOfStorageHardwareIDCollection // ================================================================== [Association, Aggregation, Description ( "MemberOfStorageHardwareIDCollection is an aggregation used " "to establish membership of StorageHardIDs (host WWNs) in a " "host.
InForm OS Version 2.3.1 CIM API Programming Reference [Override ( "Dependent" ), Weak, Description ( "The StorageHardwareID management service hosted on the " "3PAR InServ.
CIM API Programming Reference InForm OS Version 2.3.1 // ================================================================== [Description ( "3PAR PrivilegeManagementService is responsible for creating, " "deleting, and associating AuthorizedPrivilege instances. " "References to 'subject' and 'target' define the entities that " "are associated with an AuthorizedPrivilege instance via the " "relationships, AuthorizedSubject and AuthorizedTarget, " "respectively.
InForm OS Version 2.3.1 CIM API Programming Reference [Override ( "Antecedent" ), Description ( "The privilege management service which supports " "authorized privilege.")] TPD_PrivilegeManagementService REF Antecedent; [Override ( "Dependent" ), Description ( "The authorized privilege which uses the management service.
CIM API Programming Reference InForm OS Version 2.3.1 // ================================================================== [Description ( "3PAR SFP for Node FC ports.")] class TPD_SFP : CIM_PhysicalConnector { [Description ("Revision code.") ] String Revision; [Description ( "The current bandwidth of the SFP in Bits per Second."), Units ( "Bits per Second" )] uint64 Speed; [Description ("Position of the TX disable pin.
InForm OS Version 2.3.1 CIM API Programming Reference "A relationship between FCPort and it's SFP.")] class TPD_FCPortSFP : CIM_PortActiveConnection { [Override ( "Antecedent" ), Description ( "The PhysicalConnector.")] TPD_SFP REF Antecedent; [Override ( "Dependent" ), Description ( "The NetworkPort that transmits using the Connector.
CIM API Programming Reference InForm OS Version 2.3.1 Values {"FC", "SATA", "ALPHAFC"} ] uint16 CageSubType; [Description ("Position of the cage in the node."), Read ] uint16 Position; [Description ("Location of the cage.") ] string Location; [Description ("Shows if the loop is split."), Read ] boolean LoopSplit; [Description ("Chain position of the A Loop."), Read ] uint16 ChainPositionLoopA; [Description ("Chain position of the B Loop.
InForm OS Version 2.3.1 CIM API Programming Reference boolean IsPortA ); }; // ================================================================== // DC0 and DC1 TPD Drive Cage // ================================================================== [Description ( "DC0 and DC1 3PAR Drive Cage")] class TPD_DriveCageDC1 : TPD_DriveCage { [Description ("Side of the cage.
CIM API Programming Reference InForm OS Version 2.3.1 // ================================================================== // DC3 TPD Drive Cage // ================================================================== [Description ( "DC3 3PAR Drive Cage")] class TPD_DriveCageDC3 : TPD_DriveCage { [Description ("Status of the temperature sensor.
InForm OS Version 2.3.1 CIM API Programming Reference { [Description ("Position of the Interface Card in the cage.") ] uint16 Position; [Description ("Type of the cage this Interface Card is in."), ValueMap {"0", "1", "2", "3", "4"}, Values {"Unknown", "DC0", "DC1", "DC2", "DC3"} ] uint16 CageType; [Description ("Position of the Interface Card on the loop.
CIM API Programming Reference InForm OS Version 2.3.1 ValueMap {"1", "2", "4", "10"}, Values {"1G", "2G", "4G", "10G"} ] uint16 LoopBLinkSpeed[]; }; // ================================================================== // TPD Cage Interface Card for DC0 and DC1 cage // ================================================================== [Description ( "3PAR Cage Interface Card for DC0 and DC1 cage")] class TPD_CageInterfaceCardDC1 : TPD_CageInterfaceCard { [Description ("Split LED status.
InForm OS Version 2.3.1 CIM API Programming Reference [Description ("Firmware version on the Interface Card processor.") ] string FirmwareVersion; [Description ("Loop A link LED status." " Array index 0 is Loop A0, array index 1 is Loop A1."), ValueMap {"0", "1", "2"}, Values {"Off", "Amber", "Green"} ] uint16 LoopALinkLED[]; [Description ("Loop B link LED status." " Array index 0 is Loop B0, array index 1 is Loop B1.
CIM API Programming Reference InForm OS Version 2.3.1 // TPD Cage Interface Card for DC2 cage // ================================================================== [Description ( "3PAR Cage Interface Card for DC2 cage")] class TPD_CageInterfaceCardDC2 : TPD_CageInterfaceCard { [Description ("Split LED status."), ValueMap {"0", "1", "2"}, Values {"Off", "Amber", "Green"} ] uint16 SplitLED; [Description ("System LED status.
InForm OS Version 2.3.1 CIM API Programming Reference [Description ("Loop A SFP name." " Array index 0 is Loop A0, array index 1 is Loop A1.") ] string LoopASFPName[]; [Description ("Loop B SFP name." " Array index 0 is Loop B0, array index 1 is Loop B1.") ] string LoopBSFPName[]; [Description ("Loop A SFP state." " Array index 0 is Loop A0, array index 1 is Loop A1.
CIM API Programming Reference InForm OS Version 2.3.1 [Description ("Shows if the locate is ON." " Array index 0 is Loop A0, array index 1 is Loop A1.") ] boolean LoopALocateON[]; [Description ("Shows if the locate is ON." " Array index 0 is Loop B0, array index 1 is Loop B1.") ] boolean LoopBLocateON[]; // ========================================= // Operations // ========================================= [Description ( "This method causes the FC connection LED on the cage to blink.
InForm OS Version 2.3.
CIM API Programming Reference InForm OS Version 2.3.1 uint16 ESHState; [Description ("Extended State of Interface Card ESH.
InForm OS Version 2.3.1 CIM API Programming Reference [Description ("Type of the cage this magazine is in."), ValueMap {"0", "1", "2", "3", "4"}, Values {"Unknown", "DC0", "DC1", "DC2", "DC3"} ] uint16 CageType; [Description ("State of Magazine on Loop A.
CIM API Programming Reference InForm OS Version 2.3.1 boolean IsOnloop, [IN, Description ( "If true, operation performed on Port A, " "if false, operation performed on Port B. " "If not passed, operation performed on both.
InForm OS Version 2.3.
CIM API Programming Reference InForm OS Version 2.3.1 { [Description ("Position of the Sensor in the cage.") ] uint16 Position; [Description ("Sensor base unit."), Read ] string BaseUnit; [Description ("Current sensor reading (actual * 100)."), Read ] uint16 CurrentReading; [Description ("Low limit (actual * 100)."), Read ] uint16 LowLimit; [Description ("High limit (actual * 100)."), Read ] uint16 HighLimit; [Description ("Sensor state.
InForm OS Version 2.3.1 CIM API Programming Reference A.4 PAR_TPDDisk.mof This MOF contains 3PAR Disk Classes that loaded into the root/tpd namespace. (Disk Drive Lite). [Description ( "3PAR Disk Drive ")] class TPD_DiskDrive : CIM_DiskDrive { [Description ("Position of the Drive in the Magazine.") ] uint16 Position; [Description ("Type of the cage this disk is in.
CIM API Programming Reference InForm OS Version 2.3.
InForm OS Version 2.3.1 CIM API Programming Reference [Description ("Number of Spare Unused Fail chunks.") ] uint16 ChunksSpareUnusedFail; [Description ("Number of Correctable READ Errors.") ] uint64 CorrectableReadErrors; [Description ("Number of Uncorrectable READ Errors.") ] uint64 UncorrectableReadErrors; [Description ("Number of Correctable WRITE Errors.") ] uint64 CorrectableWriteErrors; [Description ("Number of Uncorrectable WRITE Errors.
CIM API Programming Reference InForm OS Version 2.3.1 [Description ("If Drive is used for ESI Channel.") ] boolean IsESI; [Description ("ESI State of Disk."), ValueMap {"0", "1", "2", "3"}, Values {"Unknown", "Not Present", "OK", "Failed"} ] uint16 ESIState; }; [Description ( "3PAR Disk Drive for DC3 cage")] class TPD_DiskDriveDC3 : TPD_DiskDrive { [Override ( "StateOnLoopA" ), Description ("State of Disk on Loop A.
InForm OS Version 2.3.
CIM API Programming Reference InForm OS Version 2.3.1 TPD_DiskDrivePackage REF Antecedent; [Override ( "Dependent" ), Description ( "The Disk Drive.
InForm OS Version 2.3.1 CIM API Programming Reference // ================================================================== [Association, Description ( "3PAR Data DiskSoftwareIdentity and DiskDrive mapping")] class TPD_DiskSoftware : CIM_ElementSoftwareIdentity { [Override ( "Antecedent" ), Description ( "The software that is installed on the Disk Drive.")] TPD_DiskSoftwareIdentity REF Antecedent; [Override ( "Dependent" ), Description ( "The Disk Drive.
CIM API Programming Reference InForm OS Version 2.3.1 TPD_StorageSystem REF GroupComponent; [Override ( "PartComponent" ), Weak, Description ( "The DiskDrive that is a component of a StorageSystem.
InForm OS Version 2.3.1 // // // CIM API Programming Reference "The target endpoint residing on a cage that connects " "to the initiator endpoint on a node.")] TPD_SCSIProtocolFCALEndpoint REF Target; // [Override ("LogicalUnit"), Description ( // "Storage extent of DiskDrive.
CIM API Programming Reference InForm OS Version 2.3.1 A.5 3PAR_TPDNode.mof This MOF contains 3PAR Node (MCS) classes that loaded into the root/tpd namespace. // // //%//////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// // // File : 3PAR_TPDNode.
InForm OS Version 2.3.1 CIM API Programming Reference [Description ("Revision part of kernel version.") ] uint16 KernelRevision; [Description ("Build part of kernel version.") ] uint16 KernelBuild; [Description ("Kernel Version in String format.") ] string KernelVersion; [Description ("Major part of BIOS version.") ] uint16 BiosMajor; [Description ("Minor part of BIOS version.") ] uint16 BiosMinor; [Description ("Revision part of BIOS version.
CIM API Programming Reference InForm OS Version 2.3.1 [Description ( "3PAR Controller Node Package for Vendor, Model, and Serial Number")] class TPD_NodePackage : CIM_PhysicalPackage { }; // ================================================================== // 3PAR NodeSystem and NodePackage association // ================================================================== [Association, Description ( "3PAR Data InServ NodeSystem and NodePackage Association.
InForm OS Version 2.3.1 CIM API Programming Reference "to all the NodePairSystem objects.")] class TPD_NodePairRedundancySet : CIM_RedundancySet { }; // ================================================================== // 3PAR NodeMemberOfSet // ================================================================== [Association, Aggregation, Description ( "TPD_NodeMemberOfSet is an aggregation used to establish " "membership of TPD_NodeSystem in a TPD_NodeRedundancySet.
CIM API Programming Reference InForm OS Version 2.3.1 " and TPD_NodeRedundancySet.")] class TPD_NodeSetIdentity : CIM_ConcreteIdentity { [Override ( "SystemElement" ), Description ( "NodePairSystem associated to the NodeRedundancySet")] TPD_NodePairSystem REF SystemElement; [Override ( "SameElement" ), Description ( "NodeRedundancySet for a NodePairSystem.
InForm OS Version 2.3.1 CIM API Programming Reference "The contained (Sub)ComputerSystem.")] TPD_NodePairSystem REF PartComponent; }; // =================================================================== // NodeComponentCS // =================================================================== [Association, Aggregation, Composition, Description ( "A ComputerSystem can aggregate another ComputerSystem. This" "class groups together TPD_StorageSystem and TPD_NodeSystem.
CIM API Programming Reference InForm OS Version 2.3.1 // ProcessorForNode // ================================================================== [Association, Aggregation, Composition, Description ( "NodeCPU aggregated by a NodeSystem.")] class TPD_ProcessorForNode : CIM_SystemDevice { [Aggregate, Override ( "GroupComponent" ), Min ( 1 ), Max ( 1 ), Description ( "The parent Node in the Association.
InForm OS Version 2.3.1 [Description ("CAS latency. string CASLatency; CIM API Programming Reference Format: CL/, in nS.") ] [Description ("JEDEC ID.") ] string JedecID; [Description ("Revision code.") ] string Revision; }; 3PAR_TPDNode.mof A.
CIM API Programming Reference InForm OS Version 2.3.1 // ================================================================== // TPD NodePackagedMemory // ================================================================== [Association, Aggregation, Description ( "A Physical Memory contained by a Node PhysicalPackage.")] class TPD_NodePackagedMemory : CIM_PackagedComponent { [Aggregate, Override ( "GroupComponent" ), Max ( 1 ), Description ( "The NodePackage that contains PhysicalMemory(s).
InForm OS Version 2.3.1 CIM API Programming Reference Description ( "The NodePackage that contains IDE Drive(s).")] TPD_NodePackage REF GroupComponent; [Override ( "PartComponent" ), Description ( "The IDE Drive which is contained in the NodePackage.")] TPD_IDEDrive REF PartComponent; }; // ================================================================== // TPD PCI Card // ================================================================== [Description ( "3PAR PCI Card.
CIM API Programming Reference InForm OS Version 2.3.1 "The PCI card that is contained in the Node Package.")] TPD_PCICard REF PartComponent; }; // ================================================================== // 3PAR SystemEndpoint: association between NodeSystem and // SCSIProtocolEndpoint // ================================================================== [Association, Description ("3PAR Data InServ NodeSystem and SCSIProtocolEndpoint association." "This is a subclass of CIM_HostedAccessPoint.
InForm OS Version 2.3.
CIM API Programming Reference InForm OS Version 2.3.1 [Description ("Position of the PS.") ] uint16 Position; [Description ("State of the AC for the power supply.
InForm OS Version 2.3.1 CIM API Programming Reference // CagePSDependency // ================================================================== [Association, Description ( "A PowerSupply is installed in a DriveCage, not for a specific Device, but " "to function with the DriveCage in general. This relationship is " "described by the TPD_CagePSDependency association.")] class TPD_CagePSDependency : CIM_PackageDependency { [Override ( "Antecedent" ), Description ( "The PowerSupply for the DriveCage.
CIM API Programming Reference InForm OS Version 2.3.1 Values {"Off", "Amber", "Green", "Amber Blinking", "Green Blinking"} ] uint16 SystemFanLED; }; // =================================================================== // PowerSupply Cooling // =================================================================== [Association, Description ( "Many Devices, such as processors or power supplies, require " "their own cooling devices.
InForm OS Version 2.3.1 CIM API Programming Reference class TPD_Battery : CIM_Battery { [Description ("Position of the Battery.") ] uint16 Position; [Description ("Maximum battery life in minutes.") ] uint32 MaxLife; [Description ("If TRUE, MAX life is low and battery is failed.") ] boolean MaxLifeLow; [Description ("Manufacturing date of the Battery.") ] datetime ManufacturingDate; [Description ("Expiration date of the Battery.") ] datetime ExpirationDate; [Description ("Charge start date of the Battery.
CIM API Programming Reference InForm OS Version 2.3.1 datetime TestStartDate[]; [Description ("The duration of the test in seconds."), ArrayType ( "Indexed" ), ModelCorrespondence {"TPD_Battery.TestStartDate", "TPD_Battery.TestPassed"} ] uint16 TestDuration[]; [Description ("TRUE if the test passed, FALSE otherwise."), ArrayType ( "Indexed" ), ModelCorrespondence {"TPD_Battery.TestStartDate", "TPD_Battery.
InForm OS Version 2.3.1 CIM API Programming Reference "The Battery.")] TPD_Battery REF Antecedent; [Override ( "Dependent" ), Description ( "The Node PowerSupply needing or associated with the Battery.
CIM API Programming Reference InForm OS Version 2.3.1 // ================================================================== // TPD_PowerSupply and CIM_ComputerSystem association // ================================================================== [Association, Aggregation, Composition, Description ( "The SystemPowerSupply association represents a relationship between " "a TPD_PowerSupply and CIM_ComputerSystem (TPD_NodeSystem or " "TPD_StorageSystem).
InForm OS Version 2.3.1 CIM API Programming Reference // ================================================================== // TPD Cage PowerSupply Sensor // ================================================================== [Association, Description ( "Many Devices include Sensors or have Sensors installed nearby, " "in order to measure critical input and output properties. This " "association indicates that relationship.
CIM API Programming Reference InForm OS Version 2.3.1 "The PhysicalElement whose Location is specified.")] TPD_SystemPackage REF Element; [Override ( "PhysicalLocation" ), Max ( 1 ), Description ( "The PhysicalElement's Location.")] TPD_SystemLocation REF PhysicalLocation; }; A.8 3PAR_TPDEthPort.mof This MOF contains 3PAR Ethernet Port classes that loaded into the root/tpd namespace.
InForm OS Version 2.3.1 CIM API Programming Reference "implemented.")] class TPD_EthPortSAPImplementation : CIM_DeviceSAPImplementation { [Override ( "Antecedent" ), Description ( "The Ethernet Port.")] TPD_EthernetPort REF Antecedent; [Override ( "Dependent" ), Description ( "The IP Protocol Endpoint implemented using the Ethernet Port.
CIM API Programming Reference InForm OS Version 2.3.1 TPD_NodeSystem REF GroupComponent; [Override ("PartComponent"), Weak, Description ( "The Ethernet Port.") ] TPD_EthernetPort REF PartComponent; }; // ================================================================== // 3PAR TCPProtocolEndpoint // ================================================================== [Description ( "A TPD protocol endpoint that is dedicated to running TCP.
InForm OS Version 2.3.1 CIM API Programming Reference { // Indicate that this is one-to-many association [Override ( "Antecedent" ), Min ( 1 ), Max ( 1 ), Description ( "The InServ node controller that hosted the protocol endpoint.")] TPD_NodeSystem REF Antecedent; [Override ( "Dependent" ), Weak, Description ( "The TCPProtocolEndpoint representing ethernet port " "on the system.")] TPD_TCPProtocolEndpoint REF Dependent; }; A.9 3PAR_TPDiSCSI.
CIM API Programming Reference InForm OS Version 2.3.1 [Override ( "Antecedent" ), Description ( "The underlying TCPProtocolEndpoint, which is depended upon.")] TPD_TCPProtocolEndpoint REF Antecedent; [Override ( "Dependent" ), Description ( "The iSCSIProtocolEndpoint dependent on the TCPProtocolEndpoint.
InForm OS Version 2.3.1 CIM API Programming Reference TPD_iSCSIProtocolEndpoint REF Dependent; }; // ================================================================== // 3PAR PrivilegeForiSCSIController // ================================================================== [Association, Description ( "PrivilegeForiSCSIController is an association used to tie the " "AuthorizedPrivileges to iSCSIController resources.
CIM API Programming Reference InForm OS Version 2.3.1 // ================================================================== // 3PAR iSCSI Protocol Controller And StorageVolume association // ================================================================== [Association, Description ( "3PAR Data InServ iSCSI protocol controller and storage volume " "association. ")] class TPD_iSCSIControllerForUnit : CIM_ProtocolControllerForUnit { [Override ("Antecedent"), Description ("The iSCSI Protocol Controller.
InForm OS Version 2.3.1 CIM API Programming Reference [Override ( "SettingData" ), Description ( "The SettingData object associated with the element.")] TPD_iSCSISessionSettings REF SettingData; }; // ================================================================== // 3PAR iSCSIConnectionSettings // ================================================================== [Description ( "The settings for the usage of an iSCSI NetworkPortal by an " "iSCSIProtcolEndpoint.
CIM API Programming Reference InForm OS Version 2.3.1 "representing iSCSI connections, which are associated to " "TCPProtocolEndpoints. Only an iSCSI initiator can create an " "iSCSI Session, an iSCSI Target MUST accept (or reject) a " "session request. EndOfNetworkPipe associates iSCSISession with " "SCSIProtocolEndpoint.
InForm OS Version 2.3.1 CIM API Programming Reference "EndpointOfNetworkPipe describes the endpoints between which a " "pipe transfers information. Whether an endpoint is a source or " "sink is indicated by a property of the association, " "SourceOrSink.")] class CIM_EndpointOfiSCSIConnection : CIM_EndpointOfNetworkPipe { [Override ( "Antecedent" ), Min ( 2 ), Max ( 2 ), Description ( "One of the endpoints of the pipe.
CIM API Programming Reference InForm OS Version 2.3.1 }; // ================================================================== // 3PAR iSCSISessionStatisticalData // ================================================================== [Association, Description ( "CIM_ElementStatisticalData is an association that relates a " "ManagedElement to its StatisticalData. Note that the " "cardinality of the ManagedElement reference is Min(1), Max(1).
InForm OS Version 2.3.1 CIM API Programming Reference "ManagedElements and their Capabilities. Note that the " "cardinality of the ManagedElement reference is Min(1), Max(1). " "This cardinality mandates the instantiation of the " "ElementCapabilities association for the referenced instance of " "Capabilities. ElementCapabilities describes the existence " "requirements and context for the referenced instance of " "ManagedElement.
CIM API Programming Reference InForm OS Version 2.3.1 [Association, Aggregation, Composition, Description ( "3PAR Data InServ Storage System and iSCSI Controller Association ") ] class TPD_SystemiSCSIController : CIM_SystemDevice { [Override ("GroupComponent"), Aggregate, Max (1), Min (1), Description( "The InServ node controller that hosted the iSCSI Controller.")] TPD_NodeSystem REF GroupComponent; [Override ("PartComponent"), Weak, Description ( "The iSCSI Controller.
InForm OS Version 2.3.1 CIM API Programming Reference // ================================================================== [Association, Description ( "CIM_ElementStatisticalData is an association that relates a " "ManagedElement to its StatisticalData. Note that the " "cardinality of the ManagedElement reference is Min(1), Max(1). " "This cardinality mandates the instantiation of the " "ElementStatisticalData association for the referenced instance " "of CIM_StatisticalData.
CIM API Programming Reference InForm OS Version 2.3.1 A.10 3PAR_TPDStats.mof This MOF contains 3PAR Statistical (Block Server Performance Subprofile) classes that loaded into the root/tpd namespace.
InForm OS Version 2.3.1 CIM API Programming Reference { }; // ================================================================== // Associated Block Statistics Manifest Collection // ================================================================== [Association, Description ( "Instances of this class associate a " "BlockStatisticsManifestCollection to the StatisticsCollection " "to which is is applied.
CIM API Programming Reference InForm OS Version 2.3.1 // ================================================================== // Member Of Block Statistics Manifest Collection // ================================================================== [Association, Aggregation, Description ( "Aggregation used to establish " "membership of ManagedElements in a Collection.
InForm OS Version 2.3.1 CIM API Programming Reference // ================================================================== [Association, Description ( "An association that relates a " "ManagedElement to its StatisticalData. Note that the " "cardinality of the ManagedElement reference is Min(1), Max(1). " "This cardinality mandates the instantiation of the " "ElementStatisticalData association for the referenced instance " "of CIM_StatisticalData.
CIM API Programming Reference InForm OS Version 2.3.1 [Key, Min ( 1 ), Max ( 1 ), Description ( "The ManagedElement for which statistical or metric data is " "defined.")] CIM_NetworkPort REF ManagedElement; [Key, Description ( "The statistic information/object.
InForm OS Version 2.3.1 CIM API Programming Reference // ================================================================== class TPD_BlockStatisticsService : CIM_BlockStatisticsService { }; // ================================================================== // Hosted Statistics Service // ================================================================== [Association, Description ( "An association between a Service and the " "System on which the functionality is located.
CIM API Programming Reference InForm OS Version 2.3.1 "ElementCapabilities association for the referenced instance of " "Capabilities. ElementCapabilities describes the existence " "requirements and context for the referenced instance of " "ManagedElement. Specifically, the ManagedElement MUST exist " "and provides the context for the Capabilities.")] class TPD_StatisticsElementCapabilities : CIM_ElementCapabilities { [Key, Min ( 1 ), Max ( 1 ), Description ( "The managed element.
InForm OS Version 2.3.1 CIM API Programming Reference Index 3PAR InForm operating environment 1.2 3PAR InServ Storage Servers 1.2 A advisories, conventions 1.4 audience 1.1 C cautions and notes 1.4 chapter summaries 1.2 CIM namespaces 4.7 CIM server disabling 4.3 enabling 4.2 CIM server status displaying 4.3 CIMNavigator 4.5 CIM-XML 2.2 commands setcim 4.2 showcim 4.2, 4.3, 4.4 showversion 4.4 startcim 4.2 stopcim 4.2, 4.3 conventions advisories 1.4 typographical 1.3 D developers 1.1 dialog elements 1.
CIM API Programming Reference R related documentation 1.2 revision history RH.1 S Service Location Protocol version 2 SLPv2 2.1, 5.3 setcim command 4.2 showcim command 4.2, 4.3, 4.4 showversion command 4.4 SLPV2 Service Location Protocol version 2 2.1, 5.3 SMI-S 2.1, 2.2 startcim command 4.2 stopcim command 4.2, 4.3 T typographical conventions 1.3 W WBEM 2.2 Distributed Management Task Force Initiative 2.2 Web-Based Enterprise Management Initiative WBEM 2.2 IX.2 Index InForm OS Version 2.3.
InForm OS Version 2.3.1 CIM API Programming Reference Revision History Release Level Revision Summary 320-200164 Rev A First release of this manual to support 3PAR InForm OS release 2.3.1. October 2009 320-200164 Rev B Added new volume options for 2.3.1, expiration and retention time. February 2010 Added support for SSD storage pool for 3.1.1, which manifests itself as an instance of StoragePool with InstanceID of “3PAR:all-SSD”. Revision History RH.
CIM API Programming Reference RH.2 InForm OS Version 2.3.
