EMC SMI-S Provider. Programmers Guide. Version 4.1 P/N REV A09. EMC Corporation Corporate Headquarters: Hopkinton, MA

Transcription

1 EMC SMI-S Provider Version 4.1 Programmers Guide P/N REV A09 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright EMC Corporation. All rights reserved. Published November 23, 2009 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 2 EMC SMI-S Provider V4.1 Programmers Guide

3 Contents Preface Chapter 1 Chapter 2 Chapter 3 Chapter 4 SMI-S Provider Overview Overview Supported features and requirements Installation and configuration About the documented examples Server Profile Server profile Server profile implementation in the EMC CIM Server Finding the top-level instance in a hierarchy Finding the SMI-S version of a Profile Array Profile Array profile Supported arrays Array synchronization Identifying when the provider's view has been synchronized Checking the array synchronization interval for an array Modifying the array synchronization interval When to modify the array synchronization interval Array synchronization and indications Array synchronization advanced parameters Valid array synchronization parameter values Replication Services Profile Replication Services Important considerations Terminology map Replication use cases Replication Service use cases Replication Service capabilities use cases Copy relationship use cases Single storage volume use cases Storage volume group use cases CLARiiON session use cases EMC SMI-S Provider V4.1 Programmers Guide 3

4 Contents Monitoring copy operations Chapter 5 Chapter 6 Block Server Performance Subprofile Block Server performance: Statistics Determining the statistics supported on an array Obtaining array statistics Statistics for an array BlockStatisticsManifest: Returning all available statistics Obtaining a Subset of all statistics: GetStatisticsCollection() Use case: Create instances and filter statistics Determine the CIM_BlockStatisticsManifestCollection instances Troubleshooting statistics when polling the provider EMC Extensions for block server performance Enabling and disabling statistics gathering in the Provider How to change refresh rates in the Provider CLARiiON-specific issues StartService() error with CLARiiON CIM_BlockStatisticsService instances Determining if statistics gathering is enabled on a CLARiiON SP Determining CLARiiON statistics capabilities Block Services Package Block Services package function Block Services components StoragePool Creating StoragePools and StorageVolumes Identifying the StoragePools hosted by a storage array Identifying from where a StoragePool is allocated Determining storage space consumed by a StoragePool Identifying storage volumes allocated from a specific StoragePool Determining the storage space consumed by a StorageVolume Increasing StoragePool capacity Decreasing StoragePool capacity Determining the RAID level of a StorageVolume Locating StorageVolumes based on Usage value Get all StorageVolumes that have a usage of Locating the fixed (potted) storage settings Identifying the available services on an array StoragePool or StorageVolume capabilities per array Identifying synchronously and asynchronously performed actions Modifying the StorageVolume ElementName EMC extensions for StoragePool StoragePool Components EMC extensions for StorageVolume RAID level EMC extensions for StorageConfigurationService CreateOrModifyElementFromStoragePool EMCReturnToStoragePool CreateOrModifyStoragePool DeleteStoragePool EMC extensions for EMC_SystemRegistrationService Locating the SystemRegistrationService Discovering all the in-band storage arrays Adding an out-of-band array to the Provider EMC SMI-S Provider V4.1 Programmers Guide

5 Contents Adding a new in-band storage array to the SMI-S Provider Synchronizing the Provider s view of an array Removing an array from SMI-S Provider Chapter 7 Chapter 8 Chapter 9 Chapter 10 Software Package Software package usage Determining the version of firmware running on an array Identifying the software version of the EMC SMI-S Provider Block Storage Views Profile Block Storage Views profile Supported views Disk Drive view Retrieving DiskDriveView instances DiskDriveView associated instances Volume view Retrieving Volume view instances VolumeView associated instances Exposed view Supported port types Retrieving the Exposed views for a storage volume or port Masking and Mapping view Supported port types Retrieving Masking and Mapping views Multiple Computer System (MCS) Subprofile MCS concepts Grouping non-top-level computer systems Traversing down the MCS hierarchy Modeling EMC arrays in MCS Modeling CLARiiON arrays Modeling Symmetrix arrays Locating system devices in an array System types for devices Understanding association differences Port and volume associations Symmetrix and CLARiiON disk association differences Determining which array a system device belongs Storage Server Asymmetry Profile Storage Server Asymmetry Storage volume failover Storage pool failover Target port failover Determining the computer system that owns a storage volume Determining the computer system that has control and access to a volume Using Storage Server Asymmetry profile with CLARiiON Handling LUN trespassing Determining if a storage volume will automatically trespass Trespassing a storage volume manually EMC Extensions for Storage Server Asymmetry Determining a LUNs default owner and current owner properties EMC SMI-S Provider V4.1 Programmers Guide 5

6 Contents Chapter 11 Chapter 12 Chapter 13 Chapter 14 Extent Composition Subprofile Extent Composition subprofile information StorageExtent Primordial StorageExtent Concrete StorageExtent Composite StorageExtent PartialAllocOfConcrete StorageExtent BaseOn association Thin Provisioning Thin Provisioning Virtual provisioning vs. thin provisioning Identifying a Symmetrix thin device or data device Locating the StoragePools reserved for Symmetrix thin provisioning Thin Provisioning on CLARiiON arrays Identifying a CLARiiON thin device Locating the StoragePools reserved for CLARiiON thin provisioning Locating thin devices allocated from a thin provisioning pool Locating data devices used as storage by the thin devices bound to a pool Locating disk drives used as storage by thin devices bound to CLARiiON pool Using Extent Composition with thinly provisioned StorageVolumes Unbound thin devices Creating Data Devices on a Symmetrix array Creating Thin Pools on a Symmetrix array and adding Pool Components Creating thin pools on CLARiiON arrays Creating Thin devices Deleting Thin devices and Data devices Symmetrix example: deleting a data device Deleting Thin Pools Volume Composition Profile Volume Composition profile Locating all CompositeExtents that represent composite volumes Locating a composite volume Determining whether a StorageVolume is a composite volume Identifying the Element Composition Service hosted by a storage array Determining the capabilities of StorageElementCompositioServices": Locating StorageVolumes that can be added to a composite volume Adding a member to an existing composite volume Creating a new composite volume Identifying a composite volume's members Creating an automated composite volume Disk Sparing Profile Disk Sparing Finding instances of StorageRedundancySet (one per array) Finding the spares storage extents on an array Finding the capabilities of the sparing implementation Locating the StorageExtent that has failed and is being spared Finding StorageExtents that have failed, but not replaced EMC SMI-S Provider V4.1 Programmers Guide

7 Contents Chapter 15 Chapter 16 Chapter 17 Storage Element Protection Profile Storage Element Protection CLARiiON arrays: limit support Masking and Mapping Subprofile Masking and Mapping subprofile Masking and Mapping differences in Symmetrix and CLARiiON arrays Masking capabilities of Symmetrix and CLARiiON arrays Managing SAN host-side initiators Assigning a view of volumes to a StorageHardwareID Symmetrix: Obtaining volumes mapped Symmetrix: Determine if a volume is mapped Symmetrix: Determine if a volume is masked-in to a specific initiator Symmetrix: Determine if a volume is masked Symmetrix: Masking views associated to mapping protocol controller Symmetrix: Protocol controller associated to masking view EMC Masking and Mapping subprofile extensions Determine if masking is enabled Determine if masking is enabled on a director s front-end port Enable masking/mapping support on ports with VCMDB/ Masking disabled Symmetrix device masking/mapping extensions Determining the type of masking VCMDB How to map/unmap a storage volume to a port Masking and mapping SCSI protocol controllers differences Symm_StorageHardwareIDManagementService::EMCInitiatorReplace Symm_StorageHardwareIDManagementService::EMCInitiatorAliasSet Symm_ControllerConfigurationService:: EMCMaskingRefresh Symmetrix use cases for masking and mapping operations Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case CLARiiON device masking/mapping extensions Clar_LunMaskingSCSIProtocolController::setProperty/modifyInstance Clar_Privilege::setProperty/modifyInstance Clar_StorageHardwareIDManagementService::CreateStorageHardwareID CLARiiON use cases for masking and mapping operations Remove storage groups example EMC Symmetrix Group Masking and Mapping Group Masking and Mapping Description MaskingGroup Class EMC SMI Provider sub-classes of MaskingGroup InitiatorMaskingGroup Consistent Logical Unit Number Properties added to the ProtocolControllerMaskingCapabilities class EMC SMI-S Provider V4.1 Programmers Guide 7

8 Contents Use Cases UC1: Create a masking view using masking groups of initiators, target ports and volumes UC2: Expose two additional volumes using the DeviceMaskingGroup from UC UC2: Remove volume access using the DeviceMaskingGroup from UC Chapter 18 Chapter 19 Chapter 20 Chapter 21 Copy Services Subprofile Copy Services Symmetrix and CLARiiON replication types Creating a replica of a source volume Determining synchronized storage volumes Identifying attributes of a synchronized storage volume relationship Additional SyncState values Target Ports Subprofile Target Ports (FC, SPI, ESCON) subprofiles Target ports on Symmetrix and CLARiiON arrays ProtocolEndpoints and LogicalPorts Determining ProtocolEndpoints of a storage processor system Determining the protocol end-point type Logical port associated to a protocol end-point Available protocol controller services for a protocol end-point iscsi Target Ports subprofile Working with network entities Determining the iscsi capabilities of a storage array Locating the iscsi nodes Identifying available iscsi ports Locating a network portal s IP address and port number Identifying what volumes are exposed through an iscsi node FC Initiator Ports Subprofile FC Initiator Port subprofile Finding the initiator ports for a given array Job Control Subprofile Job Control usage How to create a job Determining which operations are performed asynchronously How to get information about a job How to monitor a job s progress Identifying a job s task How to terminate a job How to delete a job Resolving a hung job Elements affected by a job Determining the status of a job Identifying what jobs are managed by the Provider EMC SMI-S Provider V4.1 Programmers Guide

9 Contents Chapter 22 Appendix A Access Points and Disk Drive Lite Subprofiles Access Point subprofile How to obtain the management URL for Clariion How to obtain the management URL for Symmetrix Disk Drive Lite subprofile EMC SMI-S Provider UML Diagrams Access Points Array Profile Block Server Performance Block Services Package: Pool Manipulation Block Services Package: Storage Configuration Block Services Package: Volume Creation Block Storage Views Profile: Disk Drive View Block Storage Views Profile: Exposed View Block Storage Views Profile: Masking and Mapping View Block Storage Views Profile: Volume View Copy Sevices: Local Copy Services: Remote Discovery Services Disk Drive Lite Disk Sparing Profile Extent Composition: Snap and Mirror Extent Composition: Volumes Extent Conservation: CLARiiON Arrays Extent Conservation: Symmetrix Arrays FC Initiator Port FC Target Port iscsi Target Ports Location Log Logical/Physical Array: CLARiiON Logical/Physical Array: Symmetrix Logical/Physical Disk: CLARiiON Logical/Physical Disk: Symmetrix Logical/Physical power, battery, fan, LCC for CLARiiON Arrays Logical/Physical power, battery, fan, LCC, memory for Symmetrix Arrays Logical/Physical SPCard: CLARiiON Array Logical/Physical SPCard: CLARiiON CX4 Array Logical/Physical SPCard: Symmetrix Array LUN Masking and Mapping LUN Masking and Mapping: Capabilities LUN Masking and Mapping: Privilege Multiple Computer Systems: CLARiiON Multiple Computer System: Symmetrix Server Profile: Object Manager Server profile: Registered Profile Software Package SPI Target Ports Storage Pools Storage Server Asymmetry: CLARiiON Only Thin Provisioning (Virtual Provisioning): Clariion arrays Thin Provisioning (Virtual Provisioning): Symmetrix arrays Volume Composition EMC SMI-S Provider V4.1 Programmers Guide 9

10 Contents Appendix B Appendix C Appendix D Appendix E EMC Extension Glossary EMC extensions EMC Indications Supported CQL queries Array, Health, and Block Services package FC target ports and iscsi target ports subprofile Mulitple computer system profile Copy Services and Replication Services Job control LUN masking mapping Block storage views Physical package Group Masking and Mapping Profile EMC-Specific additions Supported WQL queries Array, Health, and Block Services packages FC target ports and iscsi target ports subprofile Multiple Computer System subprofile Job control Lun masking mapping Block storage views Physical Package EMC specific additions EMC SMI-S Provider Symmetrix- and CLARiiON-specific indications CIM indication filters EMC-specific indication filters Supported lifecycle indications by class Alerts OSLSProvider.conf Controlling the EMC SMI-S Provider at runtime Restrictions and Limitations Restrictions Creating a Masking View may result in an error The CIM_StorageSynchronized association is not getting populated from target Volume Enumeration of class CIM_StorageSynchronized may result in duplicate instances 372 Pull operation limitations EMC SMI-S Provider V4.1 Programmers Guide

11 Preface As part of its effort to continuously improve and enhance the performance and capabilities of the EMC product line, EMC periodically releases new versions of EMC SMI-S Provider. Therefore, some functions described in this guide may not be supported by all versions of EMC SMI-S Provider software currently in use. For the most up-to-date information on product features, see your product release notes. If an EMC SMI-S Provider feature does not function properly or does not function as described in this guide, please contact the EMC Customer Support Center for assistance. If you are an EMC Development Partner, refer to the EMC Powerlink web site. Audience This manual is for programmers developing SMI-based client application that utilize the EMC SMI-S Provider to manage Symmetrix and CLARiiON arrays via SNIA s SMI-S V1.2. An SMI client developer using this manual is expected to have a working knowledge of the DMTF specifications, the SNIA SMI-S specification, and working knowledge of the supported EMC storage arrays (Symmetrix or CLARiiON arrays), as specified in the EMC SMI-S Provider Release Notes, V4.1. Related documentation Conventions used in this guide Other related EMC SMI-S Provider publications of interest are: EMC SMI-S Provider Programmers Release Notes, V4.1 EMC uses the following conventions for notes, cautions, warnings, and danger notices. Note: A note presents information that is important, but not hazard-related.! CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software. The following naming conventions are used in this manual: In this manual, every occurrence of the word MVS in text or in symbolic syntax means OS/390 and z/os. In this manual, every occurrence of the word OSF1 in text or in symbolic syntax means Tru64 UNIX. EMC SMI-S Provider V4.1 Programmers Guide 11

12 Preface Typographical conventions This guide uses the following type style conventions: Palatino, Boldface text provides extra emphasis and emphasizes warnings, bold and specifies window names and menu items in text. Palatino, New terms or unique word usage in text italic Applies emphasis in examples and in references to book titles and sections Courier, italic Identifies variables in a software syntax (non-literal notation) Courier A fixed space font identifies files and pathnames, and is used in command line entries, displayed text, or program listings. System prompts and displays and specific filenames or complete paths. For example: working root directory [/user/emc]: c:\program Files\EMC\Symapi\db Courier, bold Actual user entry in examples. For example: symmcfg discover Where to get help EMC support, product, and licensing information can be obtained as follows. Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at: Technical support For technical support, go to EMC WebSupport on Powerlink. To open a case on EMC WebSupport, you must be a WebSupport customer. Information about your site configuration and the circumstances under which the problem occurred is required. Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this guide to: techpub_comments@emc.com 12 EMC SMI-S Provider V4.1 Programmers Guide

13 Invisible Body Tag 1 SMI-S Provider Overview This chapter provides an overview of the EMC SMI-S Provider. Overview...14 SMI-S Provider Overview 13

14 SMI-S Provider Overview Overview EMC SMI-S Provider V4.1 supports the SNIA Storage Management Initiative (SMI), an ANSI standard for storage management. This initiative has developed a standard management interface that has culminated in a comprehensive specification (SMI-Specification or SMI-S). The SMI-S defines the open storage management interface that enables the interoperability of multiple vendor s storage management technologies for monitoring and controlling storage resources in multi-vendor SAN topologies. The SMI strives to ensure consistent data and eliminate inconsistencies between management tools by providing a unified interface to the many storage objects that must be managed in a storage environment. This enables application developers to focus on a single, standard interface for the development of management tools The SMI-S Provider is paired with the EMC CIM Object Manager Server to provide an SMI-compliant interface for EMC Symmetrix and CLARiiON arrays. The SMI-S Provider offers two types of configurations. One configuration runs on a host and provides an interface for all Symmetrix and CLARiiON arrays, shown in Figure 1. The other provides an alternative configuration for clients to communicate with the SMI-S Provider running on the Symmetrix V-Max Service Processor, shown in Figure 2. SMI Clients EMC Storage Arrays Host CIMOM (CIM Object Manager) Symmetrix EMC SMI-S Provider CLARiiON Figure 1 SMI-S Provider configuration on a host 14 EMC SMI-S Provider V4.1 Programmers Guide

15 SMI-S Provider Overview SMI Clients Symmetrix V-Max Service Processor CIMOM (CIM Object Manager) EMC SMI-S Provider Figure 2 SMI-S Provider configuration on the Symmetrix V-Max Service Processor Supported features and requirements The Solutions Enabler SMI-S Provider supports a specific SMI-S, and a certain set of profiles and subprofiles on specific operating systems. For information on supported operating systems, hardware, software, profiles, and subprofiles, refer to the EMC SMI-S Provider Release Notes, V4.1. Installation and configuration The EMC SMI-S Provider, EMC CIM Server, and required Solutions Enabler version are installed via the EMC SMI-S Provider Kit installations. Once installed, the server is started automatically. If your environment varies from the default installation, you may need to make additional configuration changes. Refer to EMC SMI-S Provider Release Notes, V4.1 for more information on setup and configuration options. About the documented examples The examples contained herein have been generated using a utility that outputs all interactions with the provider. This has been done for display purposes only and is not intended to represent an actual working application. Overview 15

16 SMI-S Provider Overview 16 EMC SMI-S Provider V4.1 Programmers Guide

17 Invisible Body Tag 2 Server Profile This chapter describes the Server profile. Server profile...18 Server Profile 17

18 Server Profile Server profile The Server profile is used to advertise the server s capabilities to clients, as well as other information to assist clients in establishing connections. The information provided by the Server profile includes: The functional areas supported by the server (SMI profiles and subprofiles). A means to navigate to the top-level instance of a functional hierarchy (for example, the CIM_ComputerSystem representing a storage array). Communication protocol information. Server profile implementation in the EMC CIM Server The Server Profile is implemented in the EMC CIMOM, not in the provider plug-in itself. Therefore instances of classes that make up the Server profile inhabit a different CIM namespace than do other classes served by the EMC CIM Server. The Server Profile instances can be found in the interop namespace. Finding the top-level instance in a hierarchy The CIM_ComputerSystem instance represents the storage array and is the top-level instance. To find the CIM_ComputerSystem, you must navigate from one of the RegisteredProfiles of interest. 1. Query SLP (Server Location Protocol) for the Interop namespace for the CIM server in question. For the EMC SMI-S Provider, that namespace will be interop. However this namespace is subject to change between releases so a well-written client will always ask SLP for the Interop namespace. 2. The client should then enumerate the instances of CIM_RegisteredProfile in the Interop namespace obtained in the previous step. 3. Identify the CIM_RegisteredProfile instance of interest by examining each instance s RegisteredName and RegisteredVersion property values. Assuming that the client is interested in locating the top-level system for a storage array, the CIM_RegisteredProfile corresponding to SMI-S V1.3 Array profile support should be identified. In this case, look through all the returned CIM_RegisteredProfile instances until the one is found whose RegisteredVersion property contains the value and whose RegisteredName property contains the value Array. 4. Once the CIM_RegisteredProfile instance corresponding to SMI-S 1.3 Array profile support is identified, follow the CIM_ElementConformsToProfile association from that instance. The result will be a collection of EMC_StorageSystem instances, one corresponding to each known storage array. Example The following example illustrates this process: (EMCProvider:5988)? ns Namespace [interop]: (EMCProvider:5988)? ei Class: CIM_RegisteredProfile DeepInheritance [true]: LocalOnly [false]: IncludeQualifiers [false]: Property to include ('-' for all)? [-]: RegisteredName 18 EMC SMI-S Provider V4.1 Programmers Guide

19 Server Profile Property to include ('-' for all)? [-]: RegisteredOrganization Property to include ('-' for all)? [-]: RegisteredVersion Property to include ('-' for all)? [-]: ++++ Testing EnumerateInstances: CIM_RegisteredProfile ++++ [... ] Instance 1: ObjectPath : ECOM_RegisteredProfile.InstanceID="Array+1.3.0" <INSTANCE CLASSNAME="ECOM_RegisteredProfile" > <PROPERTY NAME="RegisteredName" CLASSORIGIN="CIM_RegisteredProfile" PROPAGATED="true" TYPE="string"> <VALUE>Array</VALUE> </PROPERTY> <PROPERTY NAME="RegisteredOrganization" CLASSORIGIN="CIM_RegisteredProfile" PROPAGATED="true" TYPE="uint16"> <VALUE>11</VALUE> </PROPERTY> <PROPERTY NAME="RegisteredVersion" CLASSORIGIN="CIM_RegisteredProfile" PROPAGATED="true" TYPE="string"> <VALUE>1.3.0</VALUE> </PROPERTY> </INSTANCE> [... ] (EMCProvider:5988)? an ObjectPath: ECOM_RegisteredProfile.InstanceID="Array+1.3.0" Assoc Class []: CIM_ElementConformsToProfile Result Class []: CIM_ComputerSystem Role []: Result Role []: ++++ Testing AssociatorNames: ECOM_RegisteredProfile.InstanceID="Array+1.3.0" ++++ Associator Name 0: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+ APM " Associator Name 1: Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name="SYMMETRIX " Server profile 19

20 Server Profile Finding the SMI-S version of a Profile The SMI-S RegisteredProfile instance holds the version number of all the RegisteredProfile and SubProfile instances representing an SMI-S profile v1.2 or later. Each RegisteredProfile or SubProfile instance is associated with the SMI-S RegisteredProfile using the CIM_ElementConformsToProfile association. Follow the CIM_ElementConformsToProfile association from the profile of interest, specifying the resultclass as CIM_RegisteredProfile and the result role value as ConformantStandard, to get the version number of the profile. The following example illustrates this process: (EMCProvider:5988)? a ObjectPath: ECOM_RegisteredProfile.InstanceID="Array+1.3.0" Assoc Class []: CIM_ElementConformsToProfile Result Class []: CIM_RegisteredProfile Role []: ManagedElement Result Role []: ConformantStandard IncludeQualifiers [false]: IncludeClassOrigin [false]: Property to include ('-' for all, '[empty]' for no properties)? [-]: RegisteredName Property to include ('-' for all, '[empty]' for no properties)? [-]: RegisteredVersion Property to include ('-' for all, '[empty]' for no properties)? [-]: ++++ Testing Associators: ECOM_RegisteredProfile.InstanceID="Array+1.3.0" ++++ Associator 0: ObjectPath : ECOM_RegisteredProfile.InstanceID="EMC Corporation:SMI-S:1.3.0" RegisteredName = SMI-S RegisteredVersion = Note: The SMI-S RegisteredProfile instance does not exist for SMI-S profile v1.2 or earlier. RegisteredProfile instances representing an SMI-S profile with versions prior to v1.2.0 are required to use the standard's version number in the RegisteredVersion property of each RegisteredProfile (or RegisteredSubprofile) instance. 20 EMC SMI-S Provider V4.1 Programmers Guide

21 Invisible Body Tag 3 Array Profile This chapter provides information about the Array profile implemented in the EMC SMI-S Provider used to manage EMC Symmetrix and CLARiiON arrays. Array profile...22 Array synchronization...23 Array Profile 21

22 Array Profile Array profile The Array profile is used to model Symmetrix and CLARiiON storage arrays. The top-level instance representing each storage array is an EMC_StorageSystem, which is a subclass of CIM_ComputerSystem (as specified in the SMI-S Array profile). The key classes are: ComputerSystems that represent the array as a whole StorageVolumes that are equivalent to SCSI Logical Units visible to consumers StoragePools that are the allocatable/available space on the array A SCSI transport (for example, Fibre Channel or iscsi) through which LUNs are made available The Array profile makes use of the Block Services Package as well as the FC Target Ports, SPI Target Ports, and iscsi Target Ports subprofiles. Supported arrays The Array profile supports Symmetrix and CLARiiON arrays. 22 EMC SMI-S Provider V4.1 Programmers Guide

23 Array Profile Array synchronization The Array synchronization feature is a mechanism added to the provider that automatically synchronizes the provider's view of the storage arrays it manages. Array synchronization happens at a regular, configurable interval for each storage array and has a default value of one hour. Array synchronization also takes place in response to event notifications that the provider receives from the array. The Array synchronization feature was implemented in order to improve the reliability and consistency of the management information available through the SMI-S Provider. In previous versions, the SMI-S Provider's view of its managed storage arrays could diverge from the true configuration of those systems. For example a user could create a volume on an array using a management interface other than the SMI-S Provider and it would not automatically show up in a list of StorageVolume instances returned from an Enumerate Instance Names operation performed against the provider. The EMCRefreshSystem method of the EMC_SystemRegistrationService could be used to update the provider's view on a storagesystem, but that required manual intervention by an SMI-S client that had been adapted to use the EMC-specific extension.refer to EMC extensions for EMC_SystemRegistrationService on page 116 for details. Previously two main strategies existed for maintaining a consistent view in the provider: Perform an EMCRefreshSystem operation at a regular interval. Perform an EMCRefreshSystem operation in response to a received indication. The provider was enhanced to implement those two strategies itself, eliminating the need for SMI-S clients to implement these strategies. Array synchronization 23

24 Array Profile Identifying when the provider's view has been synchronized For previous versions of the provider, a client or user performed EMCRefreshSystem operations to update the provider's view of managed storage arrays. That client could then check to see if any of the data it was tracking or displaying had been updated. Since the provider now performs synchronization operations, it also sends indications to notify clients that the provider's view has been updated. This indication comes in the form of an AlertIndication, where the AlertingManagedElement property contains a reference to the StorageSystem instance representing the storage array whose management information was updated in the provider. For example: Consumer <1> received OSLS_AlertIndication Destination: Property IndicationIdentifier= Property ProviderName=com.emc.cmp.osls.se.array.Session:OSLSProvider Property SystemName=CLARiiON+APM Property SystemCreationClassName=Clar_StorageSystem Property EventTime= Property ProbableCauseDescription=Array Synchronization Operation Performed Property ProbableCause=123 Property PerceivedSeverity=2 Property AlertType=2 Property AlertingElementFormat=2 Property Description=Array Synchronization operation succeeded for array <Array type="clariion" encoding="string" value="apm " /> Property IndicationTime= Property CorrelatedIndications= Property AlertingManagedElement= r_storagesystem",name="clariion+apm " Note: When a synchronization operation updates the provider s view following an event, the CorrelatedIndications array contains the values of the IndicationIdentifier properties for any indications that were generated and delivered for that event. If the CorrelatedIndications property is absent or has no elements, then the synchronization operation was either triggered manually (such as using the EMCRefreshSystem method) or automatically through a synchronization operation performed at regular intervals. 24 EMC SMI-S Provider V4.1 Programmers Guide

25 Array Profile Checking the array synchronization interval for an array The Array synchronization interval is specified in a property of the EMC-specific class EMC_ManagementInfoSyncSettings, which is associated to the StorageSystem instance representing the array: (EMCProvider:5988)? a ObjectPath: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " Assoc Class []: CIM_ElementSettingData Result Class []: EMC_ManagementInfoSyncSettings Role []: Result Role []: IncludeQualifiers [false]: IncludeClassOrigin [false]: Property to include ('-' for all)? [-]: EMCAutomaticSyncInterval Property to include ('-' for all)? [-]: ++++ Testing Associators: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " ++++ Associators: 1 associators; repeat count 1; in seconds Associator 0: Path = Clar_ManagementInfoSyncSettings.InstanceID="CLARiiON+APM " EMCAutomaticSyncInterval = :000 In Seconds Note: The property EMCAutomaticSyncInterval has a type of datetime and is an interval value. The format of a datetime interval is specified in section of the CIM Infrastructure Specification (DMTF DSP0004). Modifying the array synchronization interval Note: These features are for advanced clients only. For most clients, the default values of modifiable properties below should not be adjusted. A client can modify the Array synchronization interval for an array by using either the SetProperty or ModifyInstance (preferred) intrinsic method to modify the EMCAutomaticSyncInterval property of the ManagementInfoSyncSettings instance for the desired storage array: (EMCProvider:5988)? gi ObjectPath: Clar_ManagementInfoSyncSettings.InstanceID="CLARiiON+APM " LocalOnly [false]: IncludeQualifiers [false]: Property to include ('-' for all)? [-]: EMCAutomaticSyncInterval Property to include ('-' for all)? [-]: ++++ Testing GetInstance: Clar_ManagementInfoSyncSettings.InstanceID="CLARiiON+APM " ++++ GetInstance Clar_ManagementInfoSyncSettings.InstanceID="CLARiiON+APM " repeat count 1 in seconds <INSTANCE CLASSNAME="Clar_ManagementInfoSyncSettings" > <PROPERTY NAME="EMCAutomaticSyncInterval" TYPE="datetime"> <VALUE> :000</VALUE> </PROPERTY> </INSTANCE> In Seconds Please press enter key to continue... (EMCProvider:5988)? mi Array synchronization 25

26 Array Profile ObjectPath: Clar_ManagementInfoSyncSettings.InstanceID="CLARiiON+APM " IncludeQualifiers [false]: Property name? [-]: EMCAutomaticSyncInterval Is EMCAutomaticSyncInterval an array? [y n (default n)]: Type[?]: datetime Value [?]: :000 Property name? [-]: ++++ Testing ModifyInstance: Clar_ManagementInfoSyncSettings.InstanceID="CLARiiON+APM " ++++ In Seconds Please press enter key to continue... (EMCProvider:5988)? gi ObjectPath: Clar_ManagementInfoSyncSettings.InstanceID="CLARiiON+APM " LocalOnly [false]: IncludeQualifiers [false]: Property to include ('-' for all)? [-]: EMCAutomaticSyncInterval Property to include ('-' for all)? [-]: ++++ Testing GetInstance: Clar_ManagementInfoSyncSettings.InstanceID="CLARiiON+APM " ++++ GetInstance Clar_ManagementInfoSyncSettings.InstanceID="CLARiiON+A PM " repeat count 1 in seconds <INSTANCE CLASSNAME="Clar_ManagementInfoSyncSettings" > <PROPERTY NAME="EMCAutomaticSyncInterval" TYPE="datetime"> <VALUE> :000</VALUE> </PROPERTY> </INSTANCE> In Seconds Please press enter key to continue... When to modify the array synchronization interval Synchronization operations can be expensive and ideally should only be performed when necessary. The default Array synchronization interval is 1 hour. If the provider is being used to manage an array whose configuration is not expected to change or if the provider is the only interface used for managing that array, then the synchronization interval could be increased or set to 0 (disabling automatic synchronization). Conversely, the client may want to shorten the Array synchronization interval if the provider is being used to manage arrays whose configuration is changing regularly or if the client application is closely monitoring frequently changing properties (for example, free space on a volume). 26 EMC SMI-S Provider V4.1 Programmers Guide

27 Array Profile Array synchronization and indications Synchronization operations are automatically initiated in response to events received from the managed storage arrays. Those events are also used to generate indications for the components of the storage arrays where the events originated. In previous versions of the provider, an indication would be delivered to a client application, then the client application might have to initiate an EMCRefreshSystem operation to see the results of the event as described in the indication (note that this case is true for configuration changes that are not made through the provider or for status changes, for example disk failure). For example, if a StorageVolume was created on a CLARiiON array through the Navisphere GUI, an SMI-S client would receive an InstCreation indication from the provider. If that client then performed an EnumerateInstanceNames operation without refreshing the provider's view of the relevant array, the StorageVolume instance specified by the InstCreation indication may not be present in the results of the enumeration operation. The provider's Array synchronization feature significantly reduces this inconsistency by performing synchronization operations whenever it receives an event from the array and, consequently, whenever the provider generates and delivers an indication. In addition, the provider waits to deliver the indication until after a synchronization operation is performed. This ensures that a client should not receive indications whose information does not match the current information available through the intrinsic operations performed against the provider. As a consequence, however, there is a delay between an event occurring on an array and the delivery of any indications that describe the event. Array synchronization advanced parameters There are two additional advanced parameters of the provider's synchronization operation that can be modified: EMCInitialSyncDelayForEvent and EMCMaxSyncDelayForEvent. Like the Array synchronization interval, they are expressed as a property that can be set in the ManagementInfoSyncSettings instance for an array. These parameters are used to control how long the provider waits after receiving an event before performing a synchronization operation and delivering any applicable indications. Synchronization operations can be expensive and events can arrive to the provider either in bursts or in a succession. Therefore, the provider waits for a period after receiving an event in case it receives other related events. If the provider receives another event during that delay window, the delay window will be reset to wait for more events. The property EMCInitialSyncDelayForEvent defines how long the provider will wait after receiving an event before performing a synchronization operation (the default value is 2 minutes). In cases where a provider continuously receives events from an array, a client does not want to be starved forever for these indications or updates to the provider's view. The property EMCMaxSyncDelayForEvent defines the maximum amount of time the provider will wait before initiating a synchronization operation in response to an event and delivering indications for that event (and all events received before the synchronization operation has begun). Array synchronization 27

28 Array Profile Valid array synchronization parameter values In general, there is no maximum value that can be assigned to the EMCAutomaticSyncInterval property, although a reasonable value should be chosen. Setting it to a value of 0 will disable Array synchronization at regular intervals (although synchronization in response to events will still take place if a client has subscribed for indications). The value for this property also must be greater than the value for the EMCMaxSyncDelayForEvent property. The EMCMaxSyncDelayForEvent property must have a value greater than the EMCInitialSyncDelayForEvent property. The acceptable range for the EMCInitialSyncDelayForEvent property is described in an instance of the class EMC_ManagementInfoSyncCapabilities. It has two properties that define the lower and upper limits for the synchronization delay for an event: EMCMinInitialSyncDelay and EMCMaxInitialSyncDelay. For example: Note: The values for EMCMaxInitialSyncDelay and EMCMinInitialSyncDelay are in the datetime interval format. In the following example, the maximum value for the EMCInitialSyncDelayForEvent property would be 30 minutes, and the minimum would be 30 seconds. (l82ab024:5988)? a ObjectPath: //l82ab024.lss.emc.com/root/emc:clar_storagesystem.creationclassname ="Clar_StorageSystem",Name="CLARiiON+APM " Assoc Class []: CIM_ElementCapabilities Result Class []: EMC_ManagementInfoSyncCapabilities Role []: Result Role []: IncludeQualifiers [false]: IncludeClassOrigin [false]: Property to include ('-' for all)? [-]: ++++ Testing Associators: //l82ab024.lss.emc.com/root/emc:clar_storagesystem.cre ationclassname="clar_storagesystem",name="clariion+apm " ++++ Associators: 1 associators; repeat count 1; in seconds Associator 0: Path = //l82ab024.lss.emc.com/root/emc:clar_managementinfosynccapabilities.instanceid="clariion +APM " InstanceID = CLARiiON+APM EMCAutomaticSynchronization = TRUE EMCEventTriggeredSynchronization = TRUE EMCMaxInitialSyncDelay = :000 EMCMinInitialSyncDelay = :000 In Seconds Please press enter key to continue... If a client needs to be updated with indications as soon as possible, then the client may consider setting lower intervals for these two properties. If the provider is managing a storage array with a large configuration, then synchronization operations could take a long time. If the EMCMaxSyncDelayForEvent property was set to an interval less than the time taken to perform a synchronization operation for an array, and the array is undergoing many changes, then the provider might operate in a state where it is constantly performing synchronization operations. This behavior may be undesirable and the values may be increased to reduce the number of synchronization operations performed. 28 EMC SMI-S Provider V4.1 Programmers Guide

29 Invisible Body Tag Replication Services Profile This chapter describes the Replication Services profile and how it is used within the EMC SMI-S Provider. Replication Services...30 Replication use cases...32 Monitoring copy operations...61 Replication Services Profile 29

30 Replication Services Profile Replication Services The Replication Services profile allows a storage system to copy data from a source element to a target element. The copy operations may be performed on elements from the same storage system or across a connection to a different storage system. Elements used in a copy operation may be grouped to facilitate the copy operation on many elements at the same time. Furthermore, the elements of a group may be declared as Consistent. Two types of synchronization views are supported. A target element may be synchronized to the current view of the source element or may be synchronized to a point-in-time view. Snapshots and clones represent a point-in-time view, while a mirror represents a current view. Two copy modes are supported: synchronous and asynchronous. In synchronous mode, the writer waits for acknowledgement that a write to the source element was processed by the target element before accepting another I/O from the host. In asynchronous mode, the writer does not wait for this acknowledgement and continues processing I/Os, enabling writes to be sent to the target element at a later time. Important considerations Review the following considerations before using the Replication Services profile: An array does not record how a StorageSynchronized relationship or a GroupSynchronized relationship was fractured or split. As a result, the CopyState of a fractured or split relationship always indicates "Fractured", regardless of whether the relationship was actually fractured or split. Typically, the StorageSynchronized or GroupSynchronized relationships are fractured or split using the ModifyReplicaSynchronization extrinsic calls with the fracture or split operation. On certain arrays, synchronization operations such as "Reverse Roles" may require the client to invoke an additional action after the operation completes, and before the synchronization relationship can be operational again. You specify this additional action in the StorageSynchronized.ProgressStatus property. For example, after the "Reverse Roles" operation completes, the client must call ModifyReplicaSynchronization (or ModifyListSynchronization) with the operation of "Resync Replica". To determine which synchronization operations require additional actions, check for such entries as "Restore operation requires fracture" and "Resync operation requires activate in the Features property of the GetSupportedFeatures method. For more information, refer to Determining the supported features on page 35. Terminology map Use the following tables to map Symmetrix- and CLARiiON-specific terminology to SMI-specific terminology. Table 4-1 CLARiiON Terminology CLARiiON SMI Description SnapView Clone Mirror - Local A synchronized local copy of the source element. MirrorView Mirror - Remote A synchronized remote copy of the source element. SnapView Session Synchronization Aspect - Local A session is the "Point-In-Time" representation of the source element. 30 EMC SMI-S Provider V4.1 Programmers Guide

31 Replication Services Profile Table 4-1 CLARiiON Terminology CLARiiON SMI Description SnapView Snap Snapshot - Local A "Point-in-Time", associated virtual copy of the source element. The target element enables visibility into a session. SanCopy Clone - Local A full, "Point-In-Time", unassociated local copy of the source element. SanCopy Clone - Remote A full, "Point-In-Time", unassociated remote copy of the source element. Table 4-2 Symmetrix Terminology Symmetrix SMI Description BCV Mirror - Local A synchronized local copy of the source element. RDF Mirror - Remote A synchronized remote copy of the source element. Snapshot Snapshot - Local A "Point-in-Time", associated virtual copy of the source element. Clone Clone - Local A full, "Point-In-Time", unassociated local copy of the source element. RCopy Clone - Remote A full, "Point-In-Time", unassociated remote copy of the source element. Replication Services 31

32 Replication Services Profile Replication use cases This section provides the following detailed Replication use cases: Replication Service use cases...32 Replication Service capabilities use cases...33 Copy relationship use cases...37 Single storage volume use cases...39 Storage volume group use cases...49 CLARiiON session use cases...57 Replication Service use cases Discovering Replication Service The replication service is associated to the top level computer system via the HostedService association. In the following example, the CIM operation AssociatorNames is used to locate the instance of a CIM_ReplicationService: (EMCProvider:5988)? an ObjectPath: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " Assoc Class []: CIM_HostedService Result Class []: CIM_ReplicationService Role []: Result Role []: ++++ Testing AssociatorNames: Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM " ++++ Associator Name 0: /root/emc:clar_replicationservice.creationclassname="clar_replicationservice",name="emcr eplicationservice",systemcreationclassname="clar_storagesystem",systemname="clariion+ APM " AssociatorNames: 1 associators; repeat count 1;return data in seconds The CIM operation GetInstance is used to examine the properties of the replication service (EMCProvider:5988)? gi ObjectPath: Clar_ReplicationService.CreationClassName="Clar_ReplicationService",Name="EMCReplicat ionservice",systemcreationclassname="clar_storagesystem",systemname="clariion+apm " LocalOnly [false]: IncludeQualifiers [false]: Property to include ('-' for all)? [-]: ++++ Testing GetInstance: Clar_ReplicationService.CreationClassName="Clar_ReplicationService",Name="EMCReplicat ionservice",systemcreationclassname="clar_storagesystem",systemname="clariion+apm " ++++ <INSTANCE CLASSNAME="Clar_ReplicationService" > <PROPERTY NAME="Name" TYPE="string"> <VALUE>EMCReplicationService</VALUE> </PROPERTY> <PROPERTY NAME="CreationClassName" TYPE="string"> <VALUE>Clar_ReplicationService</VALUE> </PROPERTY> <PROPERTY NAME="SystemName" TYPE="string"> <VALUE>CLARiiON+APM </VALUE> </PROPERTY> <PROPERTY NAME="SystemCreationClassName" TYPE="string"> 32 EMC SMI-S Provider V4.1 Programmers Guide