EMC VNX Series · PDF filePrivilege Assignment ... 134 Use Case: Well ... Celerra_SystemPackaging_CSC_PCSCS

EMC Corporation Corporate Headquarters:

Hopkinton, MA 01748-9103 1-508-435-1000

www.EMC.com

EMC VNX Series Release 8.1

SMI-S Provider Programmer’s Guide for VNX P/N 300-015-115 Rev 02

2

SMI-S Provider Programmer’s Guide for VNX

Copyright © 2015, EMC Corporation. All rights reserved.

Published February, 2015

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 regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

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.

Corporate Headquarters: Hopkinton, MA 01748-9103

3


Contents

CONTENTS .................................................................................................................................................. 3

LIST OF FIGURES...................................................................................................................................... 14

LIST OF TABLES ....................................................................................................................................... 15

INTRODUCTION ........................................................................................................................................ 24

Audience ............................................................................................................................................................. 24

Basic Requirement .............................................................................................................................................. 24

Format of Profile Chapter .................................................................................................................................... 24

Definitions and Conventions ............................................................................................................................... 24

Recommendation ................................................................................................................................................ 26

References........................................................................................................................................................... 26

ARRAY PROVIDER .................................................................................................................................... 27

SERVER PROFILE ..................................................................................................................................... 28

Overview.............................................................................................................................................................. 28

Class Diagram ..................................................................................................................................................... 29

Client Considerations .......................................................................................................................................... 29 Use Case: Viewing Server Profile implementation for EMC CIM Server .............................................................. 30 Use Case: Using model fields to populate the SLP template .............................................................................. 31

CIM Element ........................................................................................................................................................ 32 ECOM_ObjectManager .......................................................................................................................................... 33 ECOM_RegisteredProfile ....................................................................................................................................... 34 ECOM_System ........................................................................................................................................................ 34 ECOM_Namespace ................................................................................................................................................ 35 ECOM_CIMXMLCommunicationMechanism......................................................................................................... 35 ECOM_ElementConformsToProfile ........................................................................................................................ 37 ECOM_HostedService ............................................................................................................................................ 37

4


PROFILE REGISTRATION PROFILE ......................................................................................................... 38

Overview.............................................................................................................................................................. 38

Class Diagram ..................................................................................................................................................... 38

Client Consideration............................................................................................................................................ 39 Use Case: Using CIM server model to determine the supported SNIA Profiles ................................................. 39 Use Case: Finding all profiles on a server ............................................................................................................ 39 Use Case: Identifying the ManagedElement defined by a profile ....................................................................... 39 Use Case: Enumerating autonomous profiles supported by a given CIM server ............................................... 40 Use Case: Determine the SNIA version of a SMI-S Profile ................................................................................... 41

CIM Element ........................................................................................................................................................ 41 ECOM_RegisteredProfile ....................................................................................................................................... 42 ECOM_RegisteredSubProfile ................................................................................................................................. 42 ECOM_ReferencedProfile ...................................................................................................................................... 42 ECOM_SubProfileRequiresProfile ......................................................................................................................... 43 ECOM_ElementConformsToProfile ........................................................................................................................ 43

NAS HEAD PROFILE ................................................................................................................................. 44

Overview.............................................................................................................................................................. 44

Class Diagram ..................................................................................................................................................... 45

Client Considerations .......................................................................................................................................... 45 Use Case: Discovering NAS Head ......................................................................................................................... 46

CIM Element ........................................................................................................................................................ 47 Celerra_CelerraComputerSystem .......................................................................................................................... 48 Celerra_DataMoverComputerSystem ................................................................................................................... 48 Celerra_VirtualDataMoverComputerSystem ........................................................................................................ 48 Celerra_LogicalDisk ............................................................................................................................................... 49 Celerra_PrimordialStorageExtent.......................................................................................................................... 50 Celerra_NFSServer ................................................................................................................................................. 51 Celerra_CIFSServer ................................................................................................................................................ 51 Celerra_ComponentCS_CCS_DMCS...................................................................................................................... 51 Celerra_ComponentCS_CCS_VDMCS ................................................................................................................... 52 Celerra_SystemDevice_CCS_LD ............................................................................................................................ 52 Celerra_SystemDevice_CCS_PSE .......................................................................................................................... 52 Celerra_HostedDependency_DMCS_NFSS........................................................................................................... 52 Celerra_HostedDependency_DMCS_CIFSS .......................................................................................................... 52 Celerra_HostedDependency_VDMCS_CIFSS........................................................................................................ 53

BLOCK SERVICES PACKAGE .................................................................................................................. 54

Overview.............................................................................................................................................................. 54

Class Diagram ..................................................................................................................................................... 54

5


Client Considerations .......................................................................................................................................... 55 Use Case: Summarizing StoragePools and Verifying reported Capacity ............................................................ 56

CIM Element ........................................................................................................................................................ 57 Celerra_PrimordialStoragePool ............................................................................................................................. 57 Celerra_NonPrimordialStoragePool ...................................................................................................................... 58 Celerra_LogicalDisk ............................................................................................................................................... 58 Celerra_StoragePoolStorageCapabilities ............................................................................................................. 58 Celerra_LogicalDiskStorageSetting ...................................................................................................................... 59 Celerra_HostedStoragePool_CCS_PSP ................................................................................................................. 60 Celerra_HostedStoragePool_CCS_NPSP .............................................................................................................. 60 Celerra_AllocatedFromStoragePool_PSP_NPSP .................................................................................................. 61 Celerra_AllocatedFromStoragePool_NPSP_LD..................................................................................................... 61 Celerra_SystemDevice_CCS_LD ............................................................................................................................ 61

FILE SYSTEM PROFILE............................................................................................................................. 62

Overview.............................................................................................................................................................. 62

Class Diagram ..................................................................................................................................................... 62

Client Consideration............................................................................................................................................ 63 Use Case: Listing existing file systems hosted by the referencing profile ......................................................... 64 Use Case: Getting FileSystemSettings for a file system ...................................................................................... 64 Use Case: Getting the ComputerSystem that hosts a file system ...................................................................... 64 Use Case: Getting all file servers and access paths that have local access to this file system ....................... 64 Use Case: Getting the access path to a given file system on the specified file server ..................................... 64 Use Case: Getting the Local Access Settings for a given file system on the specified fileserver ..................... 64 Use Case: Getting the FileShares of a given file system on all file servers ........................................................ 65 Use Case: Getting the FileShares of a given file system on the specified file server ........................................ 65

CIM Element ........................................................................................................................................................ 65 Celerra_UxfsLocalFileSystem ................................................................................................................................ 66 Celerra_FileSystemSetting .................................................................................................................................... 67 Celerra_LocallyAccessibleFileSystemSetting ....................................................................................................... 67 Celerra_HostedFileSystem_CCS_UFS ................................................................................................................... 68 Celerra_LocalAccessAvailable_NFSS_UFS ........................................................................................................... 68 Celerra_LocalAccessAvailable_CIFSS_UFS .......................................................................................................... 68 Celerra_ElementSettingData_UFS_FSS ................................................................................................................ 68 Celerra_ElementSettingData_UFS_LAFSS ............................................................................................................ 68 Celerra_HostedDependency_NFSS_LAFSS .......................................................................................................... 69 Celerra_HostedDependency_CIFSS_LAFSS .......................................................................................................... 69

FILE STORAGE PROFILE .......................................................................................................................... 70

Overview.............................................................................................................................................................. 70

Class Diagram ..................................................................................................................................................... 70

Client Consideration............................................................................................................................................ 70

6


CIM Element ........................................................................................................................................................ 71 Celerra_ResidesOnExtent_LD_UFS ....................................................................................................................... 71

FILE EXPORT PROFILE ............................................................................................................................. 72

Overview.............................................................................................................................................................. 72

Class Diagram ..................................................................................................................................................... 72

Client Considerations .......................................................................................................................................... 73 Use Case: Listing existing FileShares on the system........................................................................................... 74

CIM Element ........................................................................................................................................................ 74 Celerra_NFSShare .................................................................................................................................................. 74 Celerra_CIFSShare ................................................................................................................................................. 75 Celerra_ExportedFileShareSetting ........................................................................................................................ 75 Celerra_HostedShare_NFSFS_NFSS ..................................................................................................................... 76 Celerra_HostedShare_CIFSFS_CIFSS .................................................................................................................... 76 Celerra_ElementSettingData_EFSS_NFSFS .......................................................................................................... 76 Celerra_ElementSettingData_EFSS_CIFSFS ......................................................................................................... 76 Celerra_SAPAvailableForElement_NFSFS_NFSPE ................................................................................................ 77 Celerra_SAPAvailableForElement_CIFSFS_CIFSPE ............................................................................................... 77 Celerra_SharedElement_NFSFS_UFS .................................................................................................................... 77 Celerra_SharedElement_CIFSFS_UFS ................................................................................................................... 77

NAS NETWORK PORT PROFILE .............................................................................................................. 78

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

Class Diagram ..................................................................................................................................................... 78

Client Considerations .......................................................................................................................................... 78

CIM Element ........................................................................................................................................................ 79 Celerra_DMEthernetPort ........................................................................................................................................ 80 Celerra_CIFSProtocolEndpoint .............................................................................................................................. 81 Celerra_NFSProtocolEndpoint ............................................................................................................................... 81 Celerra_TCPProtocolEndpoint ............................................................................................................................... 82 Celerra_IPProtocolEndpoint .................................................................................................................................. 82 Celerra_IPInterfaceSettingData ............................................................................................................................. 82 Celerra_ElementSettingData_IPPE_IPISD ............................................................................................................. 83 Celerra_HostedAccessPoint_CIFSS_CIFSPE ......................................................................................................... 83 Celerra_HostedAccessPoint_CIFSS_TCPPE .......................................................................................................... 83 Celerra_HostedAccessPoint_CIFSS_IPPE ............................................................................................................. 83 Celerra_HostedAccessPoint_NFSS_NFSPE ........................................................................................................... 84 Celerra_HostedAccessPoint_NFSS_TCPPE ........................................................................................................... 84 Celerra_HostedAccessPoint_NFSS_IPPE .............................................................................................................. 84 Celerra_BindsTo_TCPPE_CIFSPE ........................................................................................................................... 84 Celerra_BindsTo_TCPPE_NFSPE ............................................................................................................................ 84 Celerra_BindsTo_IPPE_TCPPE ............................................................................................................................... 85

7


Celerra_DeviceSAPImplementation_DMEP_IPPE ................................................................................................. 85 Celerra_DeviceSAPImplementation_DMEP_CIFSPE ............................................................................................. 85 Celerra_DeviceSAPImplementation_DMEP_NFSPE ............................................................................................. 85 Celerra_SystemDevice_DMCS_DMPE ................................................................................................................... 85 Celerra_SystemDevice_VDMCS_DMPE ................................................................................................................. 86

FILE SYSTEM MANIPULATION PROFILE ............................................................................................... 87

Overview.............................................................................................................................................................. 87

Class Diagram ..................................................................................................................................................... 87

Client Considerations .......................................................................................................................................... 87 File System Creation .............................................................................................................................................. 88 File System Modification ....................................................................................................................................... 89 File System Deletion .............................................................................................................................................. 90 Use Case: Create a locally accessible file system on a storage pool ................................................................. 91 Use Case: Increase the size of a file system ........................................................................................................ 92 Use Case: Modify the name of a file system ........................................................................................................ 93 Use Case: Delete a file system and return underlying StorageExtent ................................................................ 93 Use Case: Get locally accessible capabilities from a file server ComputerSystem ........................................... 93 Use Case: Get the local access setting for a FileSystem on a File Server ComputerSystem ............................. 93 Use Case: FileSystem manipulation supported capabilities patterns ............................................................... 93

CIM_Element ....................................................................................................................................................... 94 Celerra_FileSystemConfigurationService ............................................................................................................. 95 Celerra_FileSystemConfigurationCapabilities ..................................................................................................... 95 Celerra_UxfsFileSystemCapabilities ..................................................................................................................... 96 Celerra_LocallyAccessibleFileSystemCapabilities .............................................................................................. 96 Celerra_HostedService_CCS_FSCS ....................................................................................................................... 97 Celerra_HostedDependency_CIFS_LAFSC ............................................................................................................ 97 Celerra_HostedDependency_NFS_LAFSC ............................................................................................................. 97 Celerra_HostedDependency_CIFS_LAFSS ............................................................................................................ 97 Celerra_HostedDependency_NFS_LAFSS ............................................................................................................. 97 Celerra_ElementCapabilities_FSCS_FSC .............................................................................................................. 97 Celerra_ElementCapabilities_FSCS_LAFSC .......................................................................................................... 98 Celerra_ElementCapabilities_FSCS_FSCC ............................................................................................................ 98 Celerra_SettingsDefineCapabilities_FSC_FSS ..................................................................................................... 98 Celerra_SettingsDefineCapabilities_LAFSC_LAFSS ............................................................................................. 98

FILE EXPORT MANIPULATION PROFILE ................................................................................................ 99

Overview.............................................................................................................................................................. 99

Class Diagram ..................................................................................................................................................... 99

Client Considerations .......................................................................................................................................... 99 Supported Goal Settings ..................................................................................................................................... 100 Exported Share Creation ..................................................................................................................................... 100 Exported Share Modification .............................................................................................................................. 101

8


Exported Share Deletion...................................................................................................................................... 102 Privilege Assignment ........................................................................................................................................... 102 Use Case: File Export Manipulation Supported Capabilities Patterns ............................................................. 102 Use Case: Create a FileShare for Export ............................................................................................................. 103 Use Case: Modification of an Exported FileShare .............................................................................................. 104 Use Case: Removal of an Exported FileShare .................................................................................................... 105

CIM Element ...................................................................................................................................................... 105 Celerra_FileExportService .................................................................................................................................... 106 Celerra_FileExportCapabilities ............................................................................................................................ 107 Celerra_ExportedFileShareCapabilities .............................................................................................................. 107 Celerra_ExportedFileShareSetting ...................................................................................................................... 108 Celerra_HostedService_NFSS_FES ..................................................................................................................... 108 Celerra_HostedService_CIFSS_FES ..................................................................................................................... 108 Celerra_ElementCapabilities_FES_FEC ............................................................................................................... 108 Celerra_ElementCapabilities_FES_EFSC ............................................................................................................ 108 Celerra_SettingsDefineCapabilities_EFSC_EFSS ............................................................................................... 108 Celerra_ServiceAffectsElement_FES_NFSS ........................................................................................................ 109 Celerra_ServiceAffectsElement_FES_CIFSS ....................................................................................................... 109

MULTIPLE COMPUTER SYSTEM PROFILE ......................................................................................... 110

Overview............................................................................................................................................................ 110

Class Diagram ................................................................................................................................................... 110

Client Considerations ........................................................................................................................................ 110 Use Case: Find Top-level Computer Systems ..................................................................................................... 111 Use Case: Find the Top-level Computer System for LogicalDevice ................................................................... 111

CIM Element ...................................................................................................................................................... 111 Celerra_CelerraComputerSystem ........................................................................................................................ 113 Celerra_DataMoverComputerSystem ................................................................................................................. 113 Celerra_VirtualDataComputerSystem ................................................................................................................. 113 Celerra_PhysicalDataMoverComputerSystem ................................................................................................... 113 Celerra_PhysicalControlStationComputerSystem ............................................................................................. 114 Celerra_CelerraRedundancySet .......................................................................................................................... 114 Celerra_DataMoverRedancySet .......................................................................................................................... 115 Celerra_VirtualDataMoverRedundancySet ......................................................................................................... 115 Celerra_ComponentCS_CCS_DMCS.................................................................................................................... 115 Celerra_ComponentCS_CCS_VDMCS ................................................................................................................. 115 Celerra_ComponentCS_CCS_PDMCS ................................................................................................................. 116 Celerra_ComponentCS_CCS_PCSCS................................................................................................................... 116 Celerra_ConcreteIdentity_CCS_CRS ................................................................................................................... 116 Celerra_ConcreteIdentity_DMCS_DMRS............................................................................................................. 116 Celerra_ConcreteIdentity_VDMCS_VDMRS ........................................................................................................ 116 Celerra_MemberOfCollection_CRS_DMCS ......................................................................................................... 117 Celerra_MemberOfCollection_CRS_VDMCS ....................................................................................................... 117 Celerra_MemberOfCollection_DMRS_PDMCS.................................................................................................... 117 Celerra_MemberOfCollection_VDMRS_PDMCS ................................................................................................. 117

9


Celerra_IsSpare_DMCS_CRS ............................................................................................................................... 117 Celerra_HostedDependency_DMCS_CIFSS ........................................................................................................ 118 Celerra_HostedDependency_DMCS_NFSS......................................................................................................... 118 Celerra_HostedDependency_VDMCS_CIFSS...................................................................................................... 118

EXTENT COMPOSITION PROFILE........................................................................................................ 119

Overview............................................................................................................................................................ 119

Class Diagram ................................................................................................................................................... 120

Client Considerations ........................................................................................................................................ 120 Use Case: Traverse the virtualization hierarchy of a LogicalDisk ..................................................................... 120 Use Case: Get the Primordial Extents for a SubjectExtent ................................................................................ 120 Use Case: Find the Primordial Extents used by a Logical Disk ......................................................................... 120

CIM Element ...................................................................................................................................................... 121 Celerra_CompositeExtent .................................................................................................................................... 123 Celerra_PrimordialStorageExtent........................................................................................................................ 124 Celerra_CompositeNonPrimordialStorageExtent ............................................................................................... 124 Celerra_DecompositeNonPrimordialStorageExtent........................................................................................... 125 Celerra_RemainingStorageExtent ....................................................................................................................... 125 Celerra_BasedOn_CE_LD .................................................................................................................................... 126 Celerra_BasedOn_CNPSE_DNPSE ...................................................................................................................... 126 Celerra_BasedOn_DNPSE_DNPSE ...................................................................................................................... 127 Celerra_BasedOn_PSE_DNPSE ........................................................................................................................... 127 Celerra_BasedOn_CNPSE_RSE ........................................................................................................................... 127 Celerra_BasedOn_DNPSE_RSE ........................................................................................................................... 127 Celerra_BasedOn_PSE_RSE ................................................................................................................................ 127 Celerra_CompositeExtentBasedOn_CNPSE_CE ................................................................................................. 127 Celerra_CompositeExtentBasedOn_DNPSE_CE ................................................................................................. 128 Celerra_CompositeExtentBasedOn_CNPSE_CNPSEE ........................................................................................ 128 Celerra_CompositeExtentBasedOn_DNPSE_CNPSE .......................................................................................... 128 Celerra_CompositeExtentBasedOn_PSE_CNPSE ............................................................................................... 128

SOFTWARE PROFILE ............................................................................................................................. 129

Overview............................................................................................................................................................ 129

Class Diagram ................................................................................................................................................... 129

Client Considerations ........................................................................................................................................ 129

CIM Element ...................................................................................................................................................... 130 Celerra_CelerraSoftwareIdentity ......................................................................................................................... 130 Celerra_ControlStationSoftwareIdentity ............................................................................................................ 130 Celerra_DataMoverSoftwareIdentity................................................................................................................... 131 Celerra_InstalledSoftwareIdentity_CCS_CSI ...................................................................................................... 131 Celerra_InstalledSoftwareIdentity_PDMCS_DMSI ............................................................................................. 131 Celerra_InstalledSoftwareIdentity_PCSCS_CSSI ............................................................................................... 131

10


PHYSICAL PACKAGE PACKAGE .......................................................................................................... 133

Overview............................................................................................................................................................ 133

Class Diagram ................................................................................................................................................... 133

Client Considerations ........................................................................................................................................ 134 Use Case: Well Defined Subcomponents ........................................................................................................... 136 Use Case: Get product information for a ComputerSystem .............................................................................. 136 Use Case: Verify Physical Package Implementation .......................................................................................... 137

CIM Element ...................................................................................................................................................... 138 Celerra_CelerraChassis ....................................................................................................................................... 140 Celerra_ControlStationChassis ........................................................................................................................... 141 Celerra_DMEEnclosureChassis ........................................................................................................................... 141 Celerra_DataMoverChassis ................................................................................................................................. 142 Celerra_ClariionSPChassis .................................................................................................................................. 142 Celerra_InternalRouterChassis ........................................................................................................................... 143 Celerra_DataMoverEthernetCard ........................................................................................................................ 143 Celerra_DataMoverFCAdapterCard ..................................................................................................................... 144 Celerra_BatteryModule ........................................................................................................................................ 144 Celerra_FanModule .............................................................................................................................................. 145 Celerra_DataMoverSlot ....................................................................................................................................... 145 Celerra_CelerraProduct ....................................................................................................................................... 145 Celerra_ControlStationProduct ........................................................................................................................... 146 Celerra_DMEEnclosureProduct ........................................................................................................................... 146 Celerra_ClariionSPProduct .................................................................................................................................. 146 Celerra_DataMoverProduct ................................................................................................................................. 147 Celerra_InternalRouterProduct ........................................................................................................................... 147 Celerra_DataMoverEthernetCardProduct ........................................................................................................... 147 Celerra_DataMoverFCAdapterProduct ................................................................................................................ 148 Celerra_SystemPackaging_CC_CCS.................................................................................................................... 148 Celerra_SystemPackaging_CSC_PCSCS ............................................................................................................. 148 Celerra_SystemPackaging_DMC_PDMCS ........................................................................................................... 148 Celerra_ProductPhysicalComponent_CP_CC ..................................................................................................... 149 Celerra_ProductPhysicalComponent_CSP_CSC ................................................................................................. 149 Celerra_ProductPhysicalComponent_CSPP_CSPS ............................................................................................ 149 Celerra_ProductPhysicalComponent_DMEEP_DMEEC ...................................................................................... 149 Celerra_ProductPhysicalComponent_DMP_DMC .............................................................................................. 149 Celerra_ProductPhysicalComponent_IRP_IRC ................................................................................................... 150 Celerra_ProductPhysicalComponent_FP_FM ..................................................................................................... 150 Celerra_ProductPhysicalComponent_DMECP_DMEC ........................................................................................ 150 Celerra_ProductPhysicalComponent_DMFCACP_DMFCAC ................................................................................ 150 Celerra_PackageInChassis_CC_CSC ................................................................................................................... 150 Celerra_PackageInChassis_CC_DMEEC.............................................................................................................. 151 Celerra_PackageInChassis_CC_CSPC ................................................................................................................. 151 Celerra_PackageInChassis_DMEEC_IRC ............................................................................................................. 151 Celerra_PackageInChassis_DMEEC_DMC .......................................................................................................... 151 Celerra_PackageInChassis_DMEEC_FM ............................................................................................................. 151 Celerra_ProductParentChild_CP_CSP ................................................................................................................. 152 Celerra_ProductParentChild_CP_CSPP ............................................................................................................... 152

11


Celerra_ProductParentChild_CP_DMEEP ............................................................................................................ 152 Celerra_ProductParentChild_DMEEP_DMP ........................................................................................................ 152 Celerra_ProductParentChild_DMEEP_IRP ........................................................................................................... 152 Celerra_ProductParentChild_DMEEP_FP ............................................................................................................ 152 Celerra_SlotInChassis_DMC_DMS ...................................................................................................................... 153 Celerra_CardInSlot_DMS_DMEC ......................................................................................................................... 153 Celerra_CardInSlot_DMS_DMFCAC ..................................................................................................................... 153

HEALTH PACKAGE ................................................................................................................................ 154

Overview............................................................................................................................................................ 154

Class Diagram ................................................................................................................................................... 154


CIM Element ...................................................................................................................................................... 154

INDICATION PROFILE ........................................................................................................................... 155

Overview............................................................................................................................................................ 155

Class Diagram ................................................................................................................................................... 155

Client Considerations ........................................................................................................................................ 155 Use Case: CQL for Celerra Profiles ...................................................................................................................... 157 Use Case: Creation of IndicationFilter and ListenerDestination Instances ...................................................... 158 Use Case: Determine if the indication subscription requested already exists ................................................ 158 Use Case: Creation of IndicationSubscription Instances .................................................................................. 158 Use Case: Subscribe Indication using Client-Defined Filters ............................................................................ 159

CIM Element ...................................................................................................................................................... 159 CIM_AlertIndication ............................................................................................................................................. 160 CIM_InstCreation ................................................................................................................................................. 161 CIM_InstDeletion ................................................................................................................................................. 161 CIM_InstModification .......................................................................................................................................... 161 EMC_IndicationFilter ............................................................................................................................................ 161 EMC_ListenerDestinationCIMXML ...................................................................................................................... 162 EMC_IndicationSubscription .............................................................................................................................. 162

LOCATION PROFILE .............................................................................................................................. 163

Overview............................................................................................................................................................ 163

Class Diagram ................................................................................................................................................... 163


CIM Element ...................................................................................................................................................... 164

12


Celerra_Location .................................................................................................................................................. 164 Celerra_PhysicalElementLocation_CC_L ............................................................................................................ 165 Celerra_PhysicalElementLocation_CSC_L .......................................................................................................... 165 Celerra_PhysicalElementLocation_CSPC_L ........................................................................................................ 165 Celerra_PhysicalElementLocation_DMEEC_L ..................................................................................................... 165 Celerra_PhysicalElementLocation_DMC_L ......................................................................................................... 165 Celerra_PhysicalElementLocation_DMFCA_L ..................................................................................................... 166 Celerra_PhysicalElementLocation_DMEC_L ....................................................................................................... 166 Celerra_PhysicalElementLocation_DMS_L ......................................................................................................... 166 Celerra_PhysicalElementLocation_IRC_L ........................................................................................................... 166 Celerra_PhysicalElementLocation_FM_L ............................................................................................................ 166

FILE SERVER MANIPULATION PROFILE ............................................................................................. 167

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

Class Diagram ................................................................................................................................................... 168

Client Considerations ........................................................................................................................................ 168 Use Case: Determine if a Read-Only implementation is provided .................................................................... 170

CIM Element ...................................................................................................................................................... 170 Celerra_FileServerConfigurationService ............................................................................................................. 171 Celerra_FileServerConfigurationCapabilities ..................................................................................................... 171 Celerra_FileServerCapabilites ............................................................................................................................. 172 Celerra_FileServerSettings .................................................................................................................................. 172 Celerra_CIFSSettingData ..................................................................................................................................... 172 Celerra_NFSSettingData ...................................................................................................................................... 173 Celerra_DNSSettingData ..................................................................................................................................... 173 Celerra_NISSettingData ....................................................................................................................................... 173 Celerra_IPInterfaceSettingData ........................................................................................................................... 174 Celerra_HostedService_CCS_FSrvCS .................................................................................................................. 174 Celerra_ElementCapabilities_FSrvCS_FSC ......................................................................................................... 174 Celerra_ElementCapabilities_FSrvCS_FSCC ....................................................................................................... 174 Celerra_SettingsDefineState_NFSS_FSS ............................................................................................................ 174 Celerra_SettingsDefineState_CIFSS_FSS ........................................................................................................... 174 Celerra_ConcreteComponent_FSS_CIFSSD ........................................................................................................ 175 Celerra_ConcreteComponent_FSS_NFSSD......................................................................................................... 175 Celerra_ConcreteComponent_FSS_DNSSD ........................................................................................................ 175 Celerra_ConcreteComponent_FSS_NISSD ......................................................................................................... 175 Celerra_ConcreteComponent_FSS_IPISD ........................................................................................................... 175

SIMPLE IDENTITY MANAGEMENT PROFILE ...................................................................................... 176

Overview............................................................................................................................................................ 176

Class Diagram ................................................................................................................................................... 176

Client Consideration.......................................................................................................................................... 176 UserContact Manipulation .................................................................................................................................. 177

13


Privilege Manipulation ........................................................................................................................................ 178 Use Case: Create UserContact and Identities for a domain user ...................................................................... 180 Use Case: Get the UserContact for a specified domain user whose UserContact has been created ............. 181 Use Case: Removal of an existing UserContact ................................................................................................. 182 Use Case: Get the Privilege and UserContact by an Exported File Share ......................................................... 182 Use Case: Assign a privilege to a pair of UserContact and Exported File Share .............................................. 183 Use Case: Modify privilege to a pair of UserContact and Exported File Share ................................................. 183 Use Case: Removal of the existing privilege ...................................................................................................... 183

CIM Element ...................................................................................................................................................... 183 Celerra_AccountManagementService ................................................................................................................ 184 Celerra_UserContact ............................................................................................................................................ 184 Celerra_Identity .................................................................................................................................................... 184 Celerra_HostedService_CCS_AMS ...................................................................................................................... 185 Celerra_ServiceAffectsElement_AMS_IDY .......................................................................................................... 185 Celerra_AssignedIdentity_UC_IDY ...................................................................................................................... 185 Celerra_AssociatedPrivilege_CIFSS_IDY ............................................................................................................ 185

CONFIGURATIONS AND LIMITATIONS .............................................................................................. 186

14


List of Figures

FIGURE 1. SERVER PROFILE CLASS DIAGRAM ............................................................................................ 29 FIGURE 2. FLOWCHART OF VIEWING SERVER PROFILE IMPLEMENTATION ...................................... 30 FIGURE 3. PROFILE REGISTRATION PROFILE CLASS DIAGRAM ............................................................. 38 FIGURE 4. FLOWCHART OF ENUMERATING AUTONOMOUS PROFILES ................................................ 40 FIGURE 5. FLOWCHART OF DETERMINING SNIA VERSION OF AN SMI-S PROFILE ........................... 41 FIGURE 6. NAS HEAD CLASS DIAGRAM .......................................................................................................... 45 FIGURE 7. FLOWCHART OF NAS HEAD DISCOVERY ................................................................................... 46 FIGURE 8. BLOCK SERVICE CLASS DIAGRAM ............................................................................................... 54 FIGURE 9. FLOWCHART OF STORAGEPOOL SUMMARY AND CAPACITY VERIFICATION ................ 56 FIGURE 10. FILE SYSTEM CLASS DIAGRAM ................................................................................................... 62 FIGURE 11. FILE STORAGE CLASS DIAGRAM ................................................................................................ 70 FIGURE 12. FILE EXPORT CLASS DIAGRAM ................................................................................................... 72 FIGURE 13. NAS NETWORK CLASS DIAGRAM ............................................................................................... 78 FIGURE 14. FILE SYSTEM MANIPULATION CLASS DIAGRAM .................................................................... 87 FIGURE 15. FLOWCHART OF CREATING LOCALLY ACCESSIBLE FILE SYSTEM ON

STORAGEPOOL ............................................................................................................................................. 91 FIGURE 16. FLOWCHART OF INCREASING SIZE OF FILE SYSTEM ......................................................... 92 FIGURE 17. FLOWCHART OF MODIFYING FILESYSTEM NAME................................................................. 93 FIGURE 18. FILE EXPORT MANIPULATION CLASS DIAGRAM .................................................................... 99 FIGURE 19. FLOWCHART OF CREATING EXPORTED FILE SHARE ........................................................ 103 FIGURE 20. FLOWCHART OF MODIFYING EXPORTED FILE SHARE ...................................................... 104 FIGURE 21. FLOWCHART OF RELEASING EXPORTED FILE SHARE ..................................................... 105 FIGURE 22. MULTIPLE COMPUTER SYSTEM CLASS DIAGRAM .............................................................. 110 FIGURE 23. FLOWCHART OF FINDING TOP-LEVEL COMPUTER SYSTEM FOR LOGICALDEVICE 111 FIGURE 24. EXTENT COMPOSITION CLASS DIAGRAM.............................................................................. 120 FIGURE 25. FLOWCHART OF FINDING PRIMORDIAL EXTENTS USED BY A LOGICALDISK ............ 121 FIGURE 26. SOFTWARE CLASS DIAGRAM .................................................................................................... 129 FIGURE 27. PHYSICAL PACKAGE CLASS DIAGRAM ................................................................................... 134 FIGURE 28. FLOWCHART OF GETTING PRODUCT INFORMATION FOR COMPUTERSYSTEM....... 136 FIGURE 29. FLOWCHART OF VERIFYING PHYSICAL PACKAGE IMPLEMENTATION ......................... 137 FIGURE 30. INDICATION CLASS DIAGRAM .................................................................................................... 155 FIGURE 31. FLOWCHART OF INDICATION SUBSCRIPTION ...................................................................... 159 FIGURE 32. LOCATION CLASS DIAGRAM ...................................................................................................... 163 FIGURE 33. FILE SERVER MANIPULATION CLASS DIAGRAM .................................................................. 168 FIGURE 34. SIMPLE IDENTITY MANAGEMENT CLASS DIAGRAM ........................................................... 176 FIGURE 35. FLOWCHART OF CREATING USERCONTACT ........................................................................ 180 FIGURE 36. FLOWCHART OF GETTING USERCONTACT .......................................................................... 181 FIGURE 37. FLOWCHART OF GETTING PRIVILEGE AND USERCONTACT BY AN EXPORTED FILE

SHARE ............................................................................................................................................................ 182 FIGURE 38. FLOWCHART OF ASSIGNING PRIVILEGE TO EXPORTED FILE SHARE ......................... 183

15


List of Tables

TABLE 1. CIM ELEMENTS FOR SERVER PROFILE ........................................................................................ 32 TABLE 2. REFERENCED PROPERTIES/METHODS FOR ECOM_OBJECTMANAGER............................ 33 TABLE 3. REFERENCED PROPERTIES/METHODS FOR ECOM_REGISTEREDPROFILE .................... 34 TABLE 4. REFERENCED PROPERTIES/METHODS FOR ECOM_SYSTEM ............................................... 34 TABLE 5. REFERENCED PROPERTIES/METHODS FOR ECOM_NAMESPCAE ...................................... 35 TABLE 6. REFERENCED PROPERTIES/METHODS FOR

ECOM_CIMXMLCOMMUNICATIONMECHANISM ................................................................................... 35 TABLE 7. REFERENCED PROPERTIES/METHODS FOR ECOM_ELEMENTCONFORMSTOPROFILE

........................................................................................................................................................................... 37 TABLE 8. REFERENCED PROPERTIES/METHODS FOR ECOM_HOSTEDSERVICE ............................. 37 TABLE 9. CIM ELEMENTS FOR PROFILE REGISTRATION PROFILE ......................................................... 41 TABLE 10. REFERENCED PROPERTIES/METHODS FOR ECOM_REGISTEREDSUBPROFILE .......... 42 TABLE 11. REFERENCED PROPERTIES/METHODS FOR ECOM_REFERENCEDPROFILE ................. 42 TABLE 12. REFERENCED PROPERTIES/METHODS FOR ECOM_SUBPROFILEREQUIRESPROFILE

........................................................................................................................................................................... 43 TABLE 13. CIM ELEMENTS FOR NAS HEAD PROFILE .................................................................................. 47 TABLE 14. REFERENCED PROPERTIES/METHODS FOR CELERRA_CELERRACOMPUTERSYSTEM

........................................................................................................................................................................... 48 TABLE 15. REFERENCED PROPERTIES/METHODS FOR

CELERRA_DATAMOVERCOMPUTERSYSTEM ...................................................................................... 48 TABLE 16. REFERENCED PROPERTIES/METHODS FOR

CELERRA_VIRTUALDATAMOVERCOMPUTERSYSTEM ...................................................................... 48 TABLE 17. REFERENCED PROPERTIES/METHODS FOR CELERRA_LOGICALDISK ............................ 49 TABLE 18. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRIMORDIALSTORAGEEXTENT ........................................................................................... 50 TABLE 19. REFERENCED PROPERTIES/METHODS FOR CELERRA_NFSSERVER .............................. 51 TABLE 20. REFERENCED PROPERTIES/METHODS FOR CELERRA_CIFSSERVER ............................. 51 TABLE 21. REFERENCED PROPERTIES/METHODS FOR CELERRA_COMPONENTCS_CCS_DMCS

........................................................................................................................................................................... 51 TABLE 22. REFERENCED PROPERTIES/METHODS FOR CELERRA_COMPONENTCS_CCS_VDMCS

........................................................................................................................................................................... 52 TABLE 23. REFERENCED PROPERTIES/METHODS FOR CELERRA_SYSTEMDEVICE_CCS_LD ..... 52 TABLE 24. REFERENCED PROPERTIES/METHODS FOR CELERRA_SYSTEMDEVICE_CCS_PSE .. 52 TABLE 25. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDDEPENDENCY_DMCS_NFSS ................................................................................ 52 TABLE 26. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDDEPENDENCY_DMCS_CIFSS ............................................................................... 52 TABLE 27. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDDEPENDENCY_VDMCS_CIFSS ............................................................................ 53 TABLE 28. CIM ELEMENTS FOR BLOCK SERVICE PACKAGE .................................................................... 57 TABLE 29. REFERENCED PROPERTIES/METHODS FOR CELERRA_PRIMORDIALSTORAGEPOOL


CELERRA_NONPRIMORDIALSTORAGEPOOL....................................................................................... 58 TABLE 31. REFERENCED PROPERTIES/METHODS FOR

CELERRA_STORAGEPOOLSTORAGECAPABILITIES .......................................................................... 58 TABLE 32. REFERENCED PROPERTIES/METHODS FOR

CELERRA_LOGICALDISKSTORAGESETTING ....................................................................................... 59

16


TABLE 33. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDSTORAGEPOOL_CCS_PSP ................................................................................... 60 TABLE 34. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDSTORAGEPOOL_CCS_NPSP ................................................................................ 60 TABLE 35. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ALLOCATEDFROMSTORAGEPOOL_PSP_NPSP .............................................................. 61 TABLE 36. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ALLOCATEDFROMSTORAGEPOOL_NPSP_LD ................................................................ 61 TABLE 37. CIM ELEMENTS FOR FILE SYSTEM PROFILE ............................................................................ 65 TABLE 38. REFERENCED PROPERTIES/METHODS FOR CELERRA_UXFSLOCALFILESYSTEM ...... 66 TABLE 39. REFERENCED PROPERTIES/METHODS FOR CELERRA_FILESYSTEMSETTING ............ 67 TABLE 40. REFERENCED PROPERTIES/METHODS FOR

CELERRA_LOCALLYACCESSIBLEFILESYSTEMSETTING .................................................................. 67 TABLE 41. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDFILESYSTEM_CCS_UFS......................................................................................... 68 TABLE 42. REFERENCED PROPERTIES/METHODS FOR

CELERRA_LOCALACCESSAVAILABLE_NFS_UFS ............................................................................... 68 TABLE 43. REFERENCED PROPERTIES/METHODS FOR

CELERRA_LOCALACCESSAVAILABLE_CIFS_UFS .............................................................................. 68 TABLE 44. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTSETTINGDATA_UFS_FSS .................................................................................... 68 TABLE 45. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTSETTINGDATA_UFS_LAFSS ............................................................................... 68 TABLE 46. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDDEPENDENCY_NFS_LAFSS ................................................................................. 69 TABLE 47. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDDEPENDENCY_CIFS_LAFSS ................................................................................ 69 TABLE 48. CIM ELEMENTS FOR FILE STORAGE PROFILE ......................................................................... 71 TABLE 49. REFERENCED PROPERTIES/METHODS FOR CELERRA_RESIDESONEXTENT_LD_UFS

........................................................................................................................................................................... 71 TABLE 50. VITAL INFORMATION OF FILE SHARE SETTING........................................................................ 73 TABLE 51. CIM ELEMENTS FOR FILE EXPORT PROFILE ............................................................................ 74 TABLE 52. REFERENCED PROPERTIES/METHODS FOR CELERRA_NFSSHARE ................................. 74 TABLE 53. REFERENCED PROPERTIES/METHODS FOR CELERRA_CIFSSHARE ............................... 75 TABLE 54. REFERENCED PROPERTIES/METHODS FOR

CELERRA_EXPORTEDFILESHARESETTING ......................................................................................... 75 TABLE 55. REFERENCED PROPERTIES/METHODS FOR CELERRA_HOSTEDSHARE_NFSFS_NFSS


CELERRA_HOSTEDSHARE_CIFSFS_CIFSS .......................................................................................... 76 TABLE 57. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTSETTINGDATA_EFSS_NFSFS ............................................................................ 76 TABLE 58. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTSETTINGDATA_EFSS_CIFSFS ........................................................................... 76 TABLE 59. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SAPAVAILABLEFORELEMENT_NFSFS_NFSPE ............................................................... 77 TABLE 60. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SAPAVAILABLEFORELEMENT_CIFSFS_CIFSPE ............................................................. 77 TABLE 61. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SHAREDELEMENT_NFSFS_UFS .......................................................................................... 77 TABLE 62. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SHAREDELEMENT_CIFSFS_UFS ......................................................................................... 77 TABLE 63. DATA MOVER INTERFACE NAME FORMAT ................................................................................ 78 TABLE 64. CIM ELEMENTS FOR NAS NETWORK PORT ............................................................................... 79

17


TABLE 65. REFERENCED PROPERTIES/METHODS FOR CELERRA_DMETHERNETPORT ................ 80 TABLE 66. REFERENCED PROPERTIES/METHODS FOR CELERRA_CIFSPROTOCOLENDPOINT .. 81 TABLE 67. REFERENCED PROPERTIES/METHODS FOR CELERRA_NFSPROTOCOLENDPOINT ... 81 TABLE 68. REFERENCED PROPERTIES/METHODS FOR CELERRA_TCPPROTOCOLENDPOINT ... 82 TABLE 69. REFERENCED PROPERTIES/METHODS FOR CELERRA_IPPROTOCOLENDPOINT ........ 82 TABLE 70. REFERENCED PROPERTIES/METHODS FOR CELERRA_IPINTERFACESETTINGDATA 82 TABLE 71. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTSETTINGDATA_IPPE_IPISD ................................................................................ 83 TABLE 72. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDACCESSPOINT_CIFSS_CIFSPE ........................................................................... 83 TABLE 73. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDACCESSPOINT_CIFSS_TCPPE ............................................................................ 83 TABLE 74. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDACCESSPOINT_CIFSS_IPPE ................................................................................ 83 TABLE 75. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDACCESSPOINT_NFSS_NFSPE ............................................................................. 84 TABLE 76. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDACCESSPOINT_NFSS_TCPPE ............................................................................. 84 TABLE 77. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDACCESSPOINT_NFSS_IPPE ................................................................................. 84 TABLE 78. REFERENCED PROPERTIES/METHODS FOR CELERRA_BINDSTO_TCPPE_CIFSPE..... 84 TABLE 79. REFERENCED PROPERTIES/METHODS FOR CELERRA_BINDSTO_TCPPE_NFSPE ...... 84 TABLE 80. REFERENCED PROPERTIES/METHODS FOR CELERRA_BINDSTO_IPPE_TCPPE .......... 85 TABLE 81. REFERENCED PROPERTIES/METHODS FOR

CELERRA_DEVICESAPIMPLEMENTATION_DMEP_IPPE.................................................................... 85 TABLE 82. REFERENCED PROPERTIES/METHODS FOR

CELERRA_DEVICESAPIMPLEMENTATION_DMEP_CIFSPE .............................................................. 85 TABLE 83. REFERENCED PROPERTIES/METHODS FOR

CELERRA_DEVICESAPIMPLEMENTATION_DMEP_NFSPE ............................................................... 85 TABLE 84. REFERENCED PROPERTIES/METHODS FOR CELERRA_SYSTEMDEVICE_DMCS_DMEP


CELERRA_SYSTEMDEVICE_VDMCS_DMEP ......................................................................................... 86 TABLE 86. SIGNATURE AND PARAMETERS OF SNIA_CREATEFILESYSTEM ........................................ 89 TABLE 87. SIGNATURE AND PARAMETERS OF SNIA_MODIFYFILESYSTEM ........................................ 90 TABLE 88. SIGNATURE AND PARAMETERS OF DELETEFILESYSTEM .................................................... 90 TABLE 89. FILESYSTEM MANIPULATION SUPPORTED CAPABILITIES PATTERNS ............................. 93 TABLE 90. CIM ELEMENTS FOR FILE SYSTEM MANIPULATION PROFILE.............................................. 94 TABLE 91. REFERENCED PROPERTIES/METHODS FOR

CELERRA_FILESYSTEMCONFIGURATIONSERVICE ........................................................................... 95 TABLE 92. REFERENCED PROPERTIES/METHODS FOR

CELERRA_FILESYSTEMCONFIGURATIONCAPABILITIES .................................................................. 95 TABLE 93. REFERENCED PROPERTIES/METHODS FOR

CELERRA_UXFSFILESYSTEMCAPABILITIES......................................................................................... 96 TABLE 94. REFERENCED PROPERTIES/METHODS FOR

CELERRA_LOCALLYACCESSIBLEFILESYSTEMCAPABILITIES ........................................................ 96 TABLE 95. REFERENCED PROPERTIES/METHODS FOR CELERRA_HOSTEDSERVICE_CCS_FSCS


CELERRA_HOSTEDDEPENDENCY_CIFS_LAFSC ................................................................................ 97 TABLE 97. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDDEPENDENCY_NFS_LAFSC ................................................................................. 97 TABLE 98. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTCAPABILITIES_FSCS_FSC .................................................................................. 97

18



CELERRA_ELEMENTCAPABILITIES_FSCS_LAFSC ............................................................................. 98 TABLE 100. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTCAPABILITIES_FSCS_FSCC ............................................................................... 98 TABLE 101. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SETTINGSDEFINECAPABILITIES_FSC_FSS ..................................................................... 98 TABLE 102. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SETTINGSDEFINECAPABILITIES_LAFSC_LAFSS ............................................................ 98 TABLE 103. SUPPORTED GOAL SETTINGS FOR FILE SHARE CREATION AND MODIFICATION .... 100 TABLE 104. SIGNATURE AND PARAMETERS OF SNIA_CREATEEXPORTEDSHARE ......................... 101 TABLE 105. SIGNATURE AND PARAMETERS OF SNIA_MODIFYEXPORTEDSHARE ......................... 101 TABLE 106. SIGNATURE AND PARAMETERS OF RELEASEEXPORTEDSHARE .................................. 102 TABLE 107. FILE EXPORT MANIPULATION SUPPORTED CAPABILITIES PATTERNS ........................ 102 TABLE 108. CIM ELEMENTS FOR FILE EXPORT MANIPULATION PROFILE ......................................... 105 TABLE 109. REFERENCED PROPERTIES/METHODS FOR CELERRA_FILEEXPORTSERVICE ........ 106 TABLE 110. REFERENCED PROPERTIES/METHODS FOR CELERRA_FILEEXPORTCAPABILITIES

......................................................................................................................................................................... 107 TABLE 111. REFERENCED PROPERTIES/METHODS FOR

CELERRA_EXPORTEDFILESHARECAPABILITIES .............................................................................. 107 TABLE 112. REFERENCED PROPERTIES/METHODS FOR CELERRA_HOSTEDSERVICE_NFSS_FES


CELERRA_HOSTEDSERVICE_CIFSS_FES ........................................................................................... 108 TABLE 114. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTCAPABILITIES_FES_FEC ................................................................................... 108 TABLE 115. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTCAPABILITIES_FES_EFSC ................................................................................ 108 TABLE 116. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SETTINGSDEFINECAPABILITIES_EFSC_EFSS .............................................................. 108 TABLE 117. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SERVICEAFFECTSELEMENT_FES_NFSS ....................................................................... 109 TABLE 118. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SERVICEAFFECTSELEMENT_FES_CIFSS ...................................................................... 109 TABLE 119. CIM ELEMENTS FOR MULTIPLE COMPUTER SYSTEM PROFILE ..................................... 111 TABLE 120. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALDATAMOVERCOMPUTERSYSTEM ................................................................. 113 TABLE 121. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALCONTROLSTATIONCOMPUTERSYSTEM ..................................................... 114 TABLE 122. REFERENCED PROPERTIES/METHODS FOR CELERRA_CELERRAREDUNDANCYSET


CELERRA_DATAMOVERREDUNDANCYSET ........................................................................................ 115 TABLE 124. REFERENCED PROPERTIES/METHODS FOR

CELERRA_VITURALDATAMOVERREDUNDANCYSET ....................................................................... 115 TABLE 125. REFERENCED PROPERTIES/METHODS FOR CELERRA_COMPONENTCS_CCS_DMCS


CELERRA_COMPONENTCS_CCS_VDMCS .......................................................................................... 115 TABLE 127. REFERENCED PROPERTIES/METHODS FOR

CELERRA_COMPONENTCS_CCS_PDMCS .......................................................................................... 116 TABLE 128. REFERENCED PROPERTIES/METHODS FOR

CELERRA_COMPONENTCS_CCS_PCSCS ........................................................................................... 116 TABLE 129. REFERENCED PROPERTIES/METHODS FOR

CELERRA_CONCRETEIDENTITY_CCS_CRS ....................................................................................... 116

19



CELERRA_CONCRETEIDENTITY_DMCS_DMRS ................................................................................ 116 TABLE 131. REFERENCED PROPERTIES/METHODS FOR

CELERRA_CONCRETEIDENTITY_VDMCS_VDMRS ........................................................................... 116 TABLE 132. REFERENCED PROPERTIES/METHODS FOR

CELERRA_MEMBEROFCOLLECTION_CRS_DMCS ............................................................................ 117 TABLE 133. REFERENCED PROPERTIES/METHODS FOR

CELERRA_MEMBEROFCOLLECTION_CRS_VDMCS ......................................................................... 117 TABLE 134. REFERENCED PROPERTIES/METHODS FOR

CELERRA_MEMBEROFCOLLECTION_DMRS_PDMCS ...................................................................... 117 TABLE 135. REFERENCED PROPERTIES/METHODS FOR

CELERRA_MEMBEROFCOLLECTION_VDMRS_PDMCS ................................................................... 117 TABLE 136. REFERENCED PROPERTIES/METHODS FOR CELERRA_ISSPARE_DMCS_CRS ........ 117 TABLE 137. CIM ELEMENTS FOR EXTENT COMPOSITION PROFILE ..................................................... 121 TABLE 138. REFERENCED PROPERTIES/METHODS FOR CELERRA_COMPOSITEEXTENT .......... 123 TABLE 139. REFERENCED PROPERTIES/METHODS FOR

CELERRA_COMPOSITENONPROMORDIALSTORAGEEXTENT ...................................................... 124 TABLE 140. REFERENCED PROPERTIES/METHODS FOR

CELERRA_DECOMPOSITENONPROMORDIALSTORAGEEXTENT ................................................. 125 TABLE 141. REFERENCED PROPERTIES/METHODS FOR

CELERRA_REMAININGSTORAGEEXTENT ........................................................................................... 125 TABLE 142. REFERENCED PROPERTIES/METHODS FOR CELERRA_BASEDON_CE_LD................ 126 TABLE 143. REFERENCED PROPERTIES/METHODS FOR CELERRA_BASEDON_CNPSE_DNPSE

......................................................................................................................................................................... 126 TABLE 144. REFERENCED PROPERTIES/METHODS FOR CELERRA_BASEDON_DNPSE_DNPSE

......................................................................................................................................................................... 127 TABLE 145. REFERENCED PROPERTIES/METHODS FOR CELERRA_BASEDON_PSE_DNPSE .... 127 TABLE 146. REFERENCED PROPERTIES/METHODS FOR CELERRA_BASEDON_CNPSE_RSE .... 127 TABLE 147. REFERENCED PROPERTIES/METHODS FOR CELERRA_BASEDON_DNPSE_RSE .... 127 TABLE 148. REFERENCED PROPERTIES/METHODS FOR CELERRA_BASEDON_PSE_RSE .......... 127 TABLE 149. REFERENCED PROPERTIES/METHODS FOR

CELERRA_COMPOSITEEXTENTBASEDON_CNPSE_CE .................................................................. 127 TABLE 150. REFERENCED PROPERTIES/METHODS FOR

CELERRA_COMPOSITEEXTENTBASEDON_DNPSE_CE .................................................................. 128 TABLE 151. REFERENCED PROPERTIES/METHODS FOR

CELERRA_COMPOSITEEXTENTBASEDON_CNPSE_CNPSE .......................................................... 128 TABLE 152. REFERENCED PROPERTIES/METHODS FOR

CELERRA_COMPOSITEEXTENTBASEDON_DNPSE_CNPSE .......................................................... 128 TABLE 153. REFERENCED PROPERTIES/METHODS FOR

CELERRA_COMPOSITEEXTENTBASEDON_PSE_CNPSE ................................................................ 128 TABLE 154. CIM ELEMENTS FOR SOFTWARE PROFILE............................................................................ 130 TABLE 155. REFERENCED PROPERTIES/METHODS FOR

CELERRA_CELERRASOFTWAREIDENTITY ......................................................................................... 130 TABLE 156. REFERENCED PROPERTIES/METHODS FOR

CELERRA_CONTROLSTATIONSOFTWAREIDENTITY ....................................................................... 130 TABLE 157. REFERENCED PROPERTIES/METHODS FOR

CELERRA_DATAMOVERSOFTWAREIDENTITY ................................................................................... 131 TABLE 158. REFERENCED PROPERTIES/METHODS FOR

CELERRA_INSTALLEDSOFTWAREIDENTITY_CCS_CSI ................................................................... 131 TABLE 159. REFERENCED PROPERTIES/METHODS FOR

CELERRA_INSTALLEDSOFTWAREIDENTITY_PDMCS_DMSI .......................................................... 131 TABLE 160. REFERENCED PROPERTIES/METHODS FOR

CELERRA_INSTALLEDSOFTWAREIDENTITY_PCSCS_CSSI ........................................................... 131 TABLE 161. CIM ELEMENTS FOR PHYSICAL PACKAGE PROFILE .......................................................... 138

20


TABLE 162. REFERENCED PROPERTIES/METHODS FOR CELERRA_CELERRACHASSIS .............. 140 TABLE 163. REFERENCED PROPERTIES/METHODS FOR CELERRA_CONTROLSTATIONCHASSIS

......................................................................................................................................................................... 141 TABLE 164. REFERENCED PROPERTIES/METHODS FOR CELERRA_DMEENCLOSURECHASSIS

......................................................................................................................................................................... 141 TABLE 165. REFERENCED PROPERTIES/METHODS FOR CELERRA_DATAMOVERCHASSIS ....... 142 TABLE 166. REFERENCED PROPERTIES/METHODS FOR CELERRA_CLARIIONSPCHASSIS ........ 142 TABLE 167. REFERENCED PROPERTIES/METHODS FOR CELERRA_INTERNALROUTERCHASSIS


CELERRA_DATAMOVERETHERNETCARD ........................................................................................... 143 TABLE 169. REFERENCED PROPERTIES/METHODS FOR

CELERRA_DATAMOVERFCAADAPTERCARD ..................................................................................... 144 TABLE 170. REFERENCED PROPERTIES/METHODS FOR CELERRA_BATTERYMODULE ............... 144 TABLE 171. REFERENCED PROPERTIES/METHODS FOR CELERRA_FANMODULE ......................... 145 TABLE 172. REFERENCED PROPERTIES/METHODS FOR CELERRA_DATAMOVERSLOT .............. 145 TABLE 173. REFERENCED PROPERTIES/METHODS FOR CELERRA_CELERRAPRODUCT............ 145 TABLE 174. REFERENCED PROPERTIES/METHODS FOR CELERRA_CONTROLSTATIONPRODUCT

......................................................................................................................................................................... 146 TABLE 175. REFERENCED PROPERTIES/METHODS FOR CELERRA_DMEENCLOSUREPRODUCT

......................................................................................................................................................................... 146 TABLE 176. REFERENCED PROPERTIES/METHODS FOR CELERRA_CLARIIONSPPRODUCT ...... 146 TABLE 177. REFERENCED PROPERTIES/METHODS FOR CELERRA_DATAMOVERPRODUCT ..... 147 TABLE 178. REFERENCED PROPERTIES/METHODS FOR CELERRA_INTERNALROUTERPRODUCT


CELERRA_DATAMOVERETHERNETCARDPRODUCT ....................................................................... 147 TABLE 180. REFERENCED PROPERTIES/METHODS FOR

CELERRA_DATAMOVERFCADAPTERPRODUCT ................................................................................ 148 TABLE 181. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SYSTEMPACKAGING_CC_CCS .......................................................................................... 148 TABLE 182. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SYSTEMPACKAGING_CSC_PCSCS .................................................................................. 148 TABLE 183. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SYSTEMPACKAGING_DMC_PDMCS ................................................................................. 148 TABLE 184. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRODUCTPHYSICALCOMPONENT_CP_CC .................................................................... 149 TABLE 185. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRODUCTPHYSICALCOMPONENT_CSP_CSC............................................................... 149 TABLE 186. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRODUCTPHYSICALCOMPONENT_CSPP_CSPS ......................................................... 149 TABLE 187. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRODUCTPHYSICALCOMPONENT_DMEEP_DMEEC ................................................... 149 TABLE 188. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRODUCTPHYSICALCOMPONENT_DMP_DMC ............................................................. 149 TABLE 189. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRODUCTPHYSICALCOMPONENT_IRP_IRC .................................................................. 150 TABLE 190. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRODUCTPHYSICALCOMPONENT_FP_FM .................................................................... 150 TABLE 191. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRODUCTPHYSICALCOMPONENT_DMEEP_DMEEC ................................................... 150 TABLE 192. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PRODUCTPHYSICALCOMPONENT_DMFCACP_DMFCAC .......................................... 150

21



CELERRA_PACKAGEINCHASSIS_CC_CSC ......................................................................................... 150 TABLE 194. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_CC_DMEEC ................................................................................... 151 TABLE 195. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_CC_CSPC ....................................................................................... 151 TABLE 196. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_DMEEC_IRC .................................................................................. 151 TABLE 197. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_DMEEC_DMC ................................................................................ 151 TABLE 198. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_DMEEC_FM ................................................................................... 151 TABLE 199. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_CP_CSP .......................................................................................... 152 TABLE 200. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_CP_CSPP ....................................................................................... 152 TABLE 201. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_CP_DMEEP .................................................................................... 152 TABLE 202. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_DMEEP_DMP ................................................................................. 152 TABLE 203. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_DMEEP_IRP ................................................................................... 152 TABLE 204. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PACKAGEINCHASSIS_DMEEP_FP .................................................................................... 152 TABLE 205. REFERENCED PROPERTIES/METHODS FOR CELERRA_SLOTINCHASSIS_DMC_DMS

......................................................................................................................................................................... 153 TABLE 206. REFERENCED PROPERTIES/METHODS FOR CELERRA_CARDINSLOT_DMS_DMEC153 TABLE 207. REFERENCED PROPERTIES/METHODS FOR CELERRA_CARDINSLOT_DMS_DMFCAC

......................................................................................................................................................................... 153 TABLE 208. SUPPORTED PRE-DEFINED INDICATION FILTERS .............................................................. 155 TABLE 209. SUPPORTED LIFE CYCLE INDICATIONS ................................................................................. 156 TABLE 210. CIM ELEMENT IN INDICATION PROFILE .................................................................................. 159 TABLE 211. REFERENCED PROPERTIES/METHODS FOR CIM_ALERTINDICATION .......................... 160 TABLE 212. REFERENCED PROPERTIES/METHODS FOR CIM_INSTCREATION ................................ 161 TABLE 213. REFERENCED PROPERTIES/METHODS FOR CIM_INSTDELETION................................. 161 TABLE 214. REFERENCED PROPERTIES/METHODS FOR CIM_INSTMODIFICATION ....................... 161 TABLE 215. REFERENCED PROPERTIES/METHODS FOR EMC_INDICATIONFILTER ....................... 161 TABLE 216. REFERENCED PROPERTIES/METHODS FOR EMC_LISTENERDESTINATIONCIMXML

......................................................................................................................................................................... 162 TABLE 217. REFERENCED PROPERTIES/METHODS FOR EMC_INDICATIONSUBSCRIPTION ....... 162 TABLE 218. CIM ELEMENTS FOR LOCATION PROFILE .............................................................................. 164 TABLE 219. REFERENCED PROPERTIES/METHODS FOR CELERRA_LOCATION .............................. 164 TABLE 220. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALELEMENTLOCATION_CC_L ............................................................................. 165 TABLE 221. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALELEMENTLOCATION_CSC_L ........................................................................... 165 TABLE 222. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALELEMENTLOCATION_CSPC_L ........................................................................ 165 TABLE 223. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALELEMENTLOCATION_DMEEC_L ..................................................................... 165 TABLE 224. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALELEMENTLOCATION_DMC_L .......................................................................... 165 TABLE 225. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALELEMENTLOCATION_DMFCAC_L .................................................................. 166

22



CELERRA_PHYSICALELEMENTLOCATION_DMEC_L........................................................................ 166 TABLE 227. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALELEMENTLOCATION_DMS_L .......................................................................... 166 TABLE 228. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALELEMENTLOCATION_IRC_L ............................................................................ 166 TABLE 229. REFERENCED PROPERTIES/METHODS FOR

CELERRA_PHYSICALELEMENTLOCATION_FM_L ............................................................................. 166 TABLE 230. CIFS SETTING DATA ..................................................................................................................... 169 TABLE 231. NFS SETTING DATA....................................................................................................................... 169 TABLE 232. DNS SETTING DATA ...................................................................................................................... 169 TABLE 233. NIS SETTING DATA ........................................................................................................................ 169 TABLE 234. IP INTERFACE SETTING DATA ................................................................................................... 169 TABLE 235. CIM ELEMENTS FOR FILE SERVER MANIPULATION PROFILE ......................................... 170 TABLE 236. REFERENCED PROPERTIES/METHODS FOR

CELERRA_FILESERVERCONFIGURATIONSERVICE ......................................................................... 171 TABLE 237. REFERENCED PROPERTIES/METHODS FOR

CELERRA_FILESERVERCONFIGURATIONCAPABILITIES ................................................................ 171 TABLE 238. REFERENCED PROPERTIES/METHODS FOR CELERRA_FILESERVERCAPABILITIES

......................................................................................................................................................................... 172 TABLE 239. REFERENCED PROPERTIES/METHODS FOR CELERRA_FILESERVERSETTINGS ..... 172 TABLE 240. REFERENCED PROPERTIES/METHODS FOR CELERRA_CIFSSETTINGDATA ............. 172 TABLE 241. REFERENCED PROPERTIES/METHODS FOR CELERRA_ .................................................. 173 TABLE 242. REFERENCED PROPERTIES/METHODS FOR CELERRA_ .................................................. 173 TABLE 243. REFERENCED PROPERTIES/METHODS FOR CELERRA_ .................................................. 173 TABLE 244. REFERENCED PROPERTIES/METHODS FOR

CELERRA_HOSTEDSERVICE_CCS_FSRVCS ...................................................................................... 174 TABLE 245. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTCAPABILITIES_FSRVCS_FSC ........................................................................... 174 TABLE 246. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ELEMENTCAPABILITIES_FSRVCS_FSCS ........................................................................ 174 TABLE 247. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SETTINGSDEFINESTATE_NFSS_FSS ............................................................................... 174 TABLE 248. REFERENCED PROPERTIES/METHODS FOR

CELERRA_SETTINGSDEFINESTATE_CIFSS_FSS ............................................................................. 174 TABLE 249. REFERENCED PROPERTIES/METHODS FOR

CELERRA_CONCRETECOMPONENT_FSS_CIFSSD .......................................................................... 175 TABLE 250. REFERENCED PROPERTIES/METHODS FOR

CELERRA_CONCRETECOMPONENT_FSS_NFSSD ........................................................................... 175 TABLE 251. REFERENCED PROPERTIES/METHODS FOR

CELERRA_CONCRETECOMPONENT_FSS_DNSSD .......................................................................... 175 TABLE 252. REFERENCED PROPERTIES/METHODS FOR

CELERRA_CONCRETECOMPONENT_FSS_NISSD ............................................................................ 175 TABLE 253. REFERENCED PROPERTIES/METHODS FOR

CELERRA_CONCRETECOMPONENT_FSS_IPISSD ........................................................................... 175 TABLE 254. ASSOCIATED PRIVILEGE ............................................................................................................. 177 TABLE 255. ACTIVITIES AND PRIVILEGES MAPPING ................................................................................. 177 TABLE 256. SIGNATURE AND PARAMETERS OF GETUSERCONTACT ................................................. 177 TABLE 257. SIGNATURE AND PARAMETERS OF CREATEUSERCONTANCT ...................................... 178 TABLE 258. SIGNATURE AND PARAMETERS OF ASSIGNPRIVILEGEONEXPORTEDSHARE .......... 179 TABLE 259. CIM ELEMENTS FOR SIMPLE IDENTITY MANAGEMENT PROFILE ................................... 183 TABLE 260. REFERENCED PROPERTIES/METHODS FOR

CELERRA_ACCOUNTMANAGEMENTSERVICE ................................................................................... 184 TABLE 261. REFERENCED PROPERTIES/METHODS FOR CELERRA_USERCONTACT .................... 184

23


TABLE 262. REFERENCED PROPERTIES/METHODS FOR CELERRA_IDENTITY ................................ 184 TABLE 263. REFERENCED PROPERTIES/METHODS FOR CELERRA_HOSTEDSERVICE_CCS_AMS


CELERRA_SERVICEAFFECFTSELEMENT_AMS_IDY ........................................................................ 185 TABLE 265. REFERENCED PROPERTIES/METHODS FOR CELERRA_ASSIGNEDIDENTITY_UC_IDY


CELERRA_ASSOCIATEDPRIVILEGE_CIFSS_IDY ............................................................................... 185

24


Introduction

Audience

This document provides client developers with the information about the SMI-S Interface in EMC VNX for File storage system and enables them to manage a VNX file storage system.

Proper audiences are listed but not limited to the followings:

VNX File Storage System Client Developer

VNX File Storage System Functional Tester

Basic Requirement

User of this document should be familiar with CIM, WBEM, CIM/XML, SNIA and SMI-S.

Format of Profile Chapter

Each profile chapter contains the following sections:

Overview - A simple overview and introduction about the captioned profile.

Class Diagram - UML diagrams based on implementation level.

Client Considerations - Vital information, Key design principles, System characteristics, Programming tips and Use cases.

Flowcharts and/or working flow descriptions are included in each use case to demonstrate the usage of functions specified in the profile to perform information retrieval and system management.

CIM Element - Description of implemented classes and associations.

Definitions and Conventions

1. The prefix CIM_ of class name will be omitted if there is no confusion.

2. The following terminology and operations are frequently used in the flowcharts and the descriptions of use cases.

Enumerate

Invoke the intrinsic method EnumerateInstanceNames or EnumerateInstances to get all Instance-Names (model path) or Instances of a CIM Class in the target Namespace.

Flowchart Element Process Description

EnumerateInstances of CIM_RegisteredProfile in

interop namespace

EnumerateInstances of <Class-Name> in <Namespace-Name> namespace

25


EnumerateInstanceNames of CIM_RegisteredProfile in

interop namespace

EnumerateInstanceNames of <Class-Name> in <Namespace-Name> namespace

Traverse

Invoke the intrinsic method AssociatorNames or Associators to get all the Instance-Names or Instances associated to a particular source Instance via a given Association Class.


EMC CIM ObjectManager (ECOM) Discovered

Traverse CIM_NamespaceInManager to CIM_Namespace(Dependent)

Traverse <Association-Class-Name> to <Result-Class-Name>(<Result-Role>)

Example: User can traverse CIM_NamespaceInManager (Association Class) from instance of CIM_Service (Source Instance represents ObjectManager) to CIM_Namespace (Result Class) to get all namespaces managed by CIM ObjectManager.

Reference

Invoke the intrinsic method ReferenceNames or References to get all the Instance-Names or Instances of an Association Class that refers to a particular source Instance.


EMC CIM ObjectManager (ECOM) Discovered

Reference CIM_NamespaceInManager(Antecedent)

Reference <Association-Class-Name> (<Role>)

Example: User can reference CIM_NamespaceInManager (Association Class) from the instance of CIM_Service (Source Instance that represents ObjectManager) to get all instances of CIM_NamespaceInManager that refers to the ObjectManager.

Invoke Method

Invoke an intrinsic method or an extrinsic method defined in a CIM Class.


Invoke CreateInstanceOn CIM_IndicationFilter

Invoke <Intrinsic-Method> on <Class-Name>

Invoke MethodCIM_Service.Run()

Invoke <Class-Name>.<Method-Name>

26


Recommendation

1. For the performance consideration, it is recommended that client should invoke EnumerateInstanceNames, AssociatorNames and ReferenceNames instead of EnumerateInstances, Associators and References if non-key properties are not needed.

2. For the performance consideration, it is recommended that client should invoke Associators or AssociatorNames to retrieve instances of object class instead of invoking EnumerateInstances or EnumerateInstanceNames on the object class directly.

3. For the performance consideration, it is recommended that client should invoke References or ReferenceNames to retrieve instances of association class instead of invoking EnumerateInstances or EnumerateInstanceNames on the association class directly.

References

1. Distributed Management Task Force (DMTF): http://www.dmtf.org

2. Common Information Model (CIM): http://www.dmtf.org/standards/cim/

3. Web Based Enterprise Management (WBEM) Specification: http://www.dmtf.org/standards/wbem/

4. Storage Management Initiative (SMI): http://www.snia.org/smi/home

5. SMI Specification: http://www.snia.org/tech_activities/standards/curr_standards/smi

6. Service Location Protocol: http://www.ietf.org/rfc/rfc2165.txt

7. SNIA Conformance Testing Program (CTP): http://www.snia.org/ctp/

http://www.dmtf.org/

http://www.dmtf.org/standards/cim/

http://www.dmtf.org/standards/wbem/

http://www.snia.org/smi/home

http://www.snia.org/tech_activities/standards/curr_standards/smi

http://www.ietf.org/rfc/rfc2165.txt

http://www.snia.org/ctp/

27


Array Provider

The SMI-S Provider is the array provider which is built in the VNX family storage system. The profiles of the array provider allow a client application to retrieve information about a VNX family storage system, and to modify the configuration of the storage system.

There is also a server profile that is used to advertise the server capabilities to clients and to provide clients with informational assistance in establishing connections. The server profile is implemented in the EMC CIMOM (ECOM), not in the SMI-S Provider plug-in.

28


Server Profile

Overview

A CIM Server supports the CIM-XML protocol or the other WBEM protocols. The Server Profile is mandatory to all compliant SMI-S servers.

The object manager part of the model defines the capabilities of a CIM object manager (CIMOM) based on the communication mechanisms that it supports. The namespace model of the Server Profile describes the namespaces managed by the object manager and the type information contained within the namespace. The main information provided in the namespace part of the model is the namespace itself and its association to the ObjectManager. The InteropNamespace refers to the first namespace found in the InteropSchemaNamespace attribute of the SLP Template.

A Server is modeled as a System with a HostedService association to an ObjectManager. The ObjectManager is subclassified from Service. Implementations shall support an ElementConformsToProfile association referencing the RegisteredProfile for the Server Profile and the ObjectManager (rather than CIM_System which is common in the other profiles).

It is mandatory that all namespaces supported by the Server be identified (as the Namespace class) and associated to the ObjectManager via the NamespaceInManager association.

The communication protocol is CIM-XML. This class is associated to the ObjectManager via the CommMechanismForManager association.

The Profile Registration Profile describes the set of classes, associations and profiles supported by the ObjectManager. The Profile Registration Profile is required by the Server Profile.

NOTE: For more details, refer to Clause 40: Server Profile in Storage Management Technical Specification, Part 2 Common Profiles, Version 1.6.0, Revision 4.

29


Class Diagram

Figure 1. Server Profile Class Diagram

Client Considerations

Server Profile Version

Implemented in ECOM_RegisteredProfile(Server).RegisteredVersion.

ECOM Version

Implemented in ECOM_SoftwareIdentity.VersionString associated with ECOM_RegisteredProfile(Server) via ECOM_ElementSoftwareIdentity.

CIM Server Hostname

Implemented in ECOM_System.Name.

Managed Namespace

Implemented in ECOM_Namespace.Name associated with ECOM_ObjectManager via ECOM_NamespaceInManager.

Communication Mechanism

VNX SMI-S Provider supports only CIM-XML protocol.

30


Use Case: Viewing Server Profile implementation for EMC CIM Server

This use case describes how to view the Server Profile implementation for EMC CIM Server including discovering ECOM (EMC CIM Object Manager) and getting SoftwareIdentity, CIM Server, Namespace, and Communication Protocol.

Use Case: View Server Profile Implementation

Get Object Manager

Get Server Registered Profile

Get Communication Protocol

Get Managed Namespaces

Get CIM Server

Get Software Info

Start

Connect to CIM Server


interop namespace

Filter out CIM_RegisteredProfile instance for Server Profile

Conditions: AdvertiseTypes is {3:SLP} and RegisteredName is {“Server”}

Traverse CIM_ElementConformsToProfile

to CIM_Service

Got instance

Error

N

Got instanceN

Y

Traverse CIM_ElementSoftwareIdentity to CIM_SoftwareIdentity

Traverse CIM_HosteService to CIM_System

Traverse CIM_NamespaceInManager to CIM_Namespace

Traverse CIM_CommMechanismForManager to CIM_ObjectManagerCommunicationMechanism

Y

Done

RegisteredProfile for Server Profile

EMC CIM ObjectManager (ECOM)

Figure 2. Flowchart of Viewing Server Profile Implementation

31


Use Case: Using model fields to populate the SLP template

This use case describes where users can get the data to populate the SLP template in the CIM Server profile to advertise the supported SMI-S profiles.

The SLP template fields can be populated as follows:

template-url-syntax: =string

The following quotation is from WBEM SLP Template v1.0.0.

“The template-url-syntax MUST be the WBEM URI Mapping of the location of one service access point offered by the WBEM Server over TCP transport. This attribute must provide sufficient addressing information so that the WBEM Server can be addressed directly using the URL.

The WBEM URI Mapping is defined in the WBEM URI Mapping Specification 1.0.0 (DSP0207). Example: (template-url-syntax=https://localhost:5989)”

service-hi-name:

ObjectManager.ElementName

service-hi-description:

ObjectManager.Description

service-id:

ObjectManager.Name

CommunicationMechanism:

ObjectManagerCommunicationMechanism.CommunicationMechanism

OtherCommunicationMechanism:

ObjectManagerCommunicationMechanism.OtherCommunicationMechanism

InteropSchemaNamespace:

Namespace.Name for the InteropNamespace

ProtocolVersion:

ObjectManagerCommunicationMechanism.Version

MultipleOperationsSupported:

ObjectManagerCommunicationMechanism.MultipleOperationsSupported

AuthenticationMechanismSupported:

ObjectManagerCommunicationMechanism.AuthenticationMechanismsSupported

OtherAuthenticationDescription:

ObjectManagerCommunicationMechanism.AuthenticationMechanismDescriptions

Namespace:

Namespace.Name for each Namespace instance supported

Classinfo:

Namespace.Classinfo for each Namespace instance

RegisteredProfilesSupported:

A list of profiles supported by the CIM providers running in this CIM Server. Each entry in this list is separated by a comma and consists of two or three sub-fields, separated by colons. If an entry refers to a

http://www.dmtf.org/sites/default/files/standards/documents/wbem.1.0.en

32


supported profile defined in a RegisteredProfile (and not RegisteredSubProfile) instance, the format shall be:

Organization:Name

in which Organization is the name of the organization that defined the profile (e.g., SNIA or DMTF) and Name refers to the name of the profile. Note that the first format applies to autonomous or component profiles defined using RegisteredProfile. If an entry refers to a supported sub-profile defined in a RegisteredSubProfile instance, the format shall be:

Organization:Name:Subprofile-Name

in which Organization is the name of the organization that defined the profile (e.g., SNIA or DMTF), Name refers to the name of the profile, and Subprofile-Name is the name of the sub-profile.

For either format, Organization shall be identical to the RegisteredOrganization attribute in the appropriate RegisteredProfile instance. For the first format, Name shall be identical to the RegisteredName attribute in the appropriate RegisteredProfile instance. For the second format:

Subprofile-Name shall be identical to the RegisteredName attribute in the appropriate RegisteredSubProfile instance.

Name shall be identical to the RegisteredName attribute in the RegisteredProfile referenced by the RegisteredSubProfile.

NOTE: For further information about getting instances containing required fields, refer to Use Case: View Server Profile implementation for EMC CIM Server.

CIM Element

The implemented classes and associations related to the Server Profile in VNX File Storage System can be described as follows:

Table 1. CIM Elements for Server Profile

CIM Class Implemented Class Description

CIM_CIMXMLCommunicationMechanism

ECOM_CIMXMLCommunicationMechanism

CIMXML communication protocols supported by ECOM.

CIM_CommMechanismForManager

ECOM_CommMechanismForManager

Associates the communication protocols to the ObjectManager.

CIM_ElementConformsToProfile

ECOM_ElementConformsToProfile

Associates the ObjectManager to the registered profile for Server Profile.

CIM_HostedService ECOM_HostedService Associates the ObjectManager to the EMC CIM Server that is hosting the ObjectManager.

CIM_Namespace ECOM_Namespace Namespaces managed by ECOM.

CIM_NamespaceInManager ECOM_NamespaceInManager

Associates the Namespaces to the ObjectManager which manages the Namespaces.

CIM_ObjectManager ECOM_ObjectManager EMC CIM Object Manager (ECOM).

33


CIM_ObjectManagerCommunicationMechanism

ECOM_OtherCommunicationMechanism

Other communication protocols supported by ECOM.

CIM_RegisteredProfile ECOM_RegisteredProfile (Server)

Registered profile for Server Profile.

CIM_System ECOM_System EMC CIM Server.

ECOM_ObjectManager

Table 2. Referenced Properties/Methods for ECOM_ObjectManager

CIM Property Description/Notes

SystemCreationClassName CreationClassName of the scoping system.

SystemName The name of the scoping system.

CreationClassName The name of the class used to create this instance.

Name A string that uniquely identifies the ObjectManager.

Caption The short textual description of the object.

Description The description of the CIM Server for human interface.

ElementName The name of the CIM Server.

EnabledDefault Default or startup configuration for the EnabledState of the ObjectManager.

EnabledState Enabled and disabled states of the ObjectManager.

GatherStatisticalData Used to control the gathering of statistical data made accessible through the CIM_CIMOMStatisticalData objects.

OperationalStatus Current operational status of the ObjectManager.

OtherEnabledState A string that describes the enabled or disabled state of the element when the EnabledState property is set to {1: Other}.

PrimaryOwnerContact Contact information of the primary owner of this computer system.

PrimaryOwnerName The name of the primary owner of this computer system.

RequestedState The last requested or desired state for the ObjectManager.

Started Whether the Sevice has been started (TRUE) or stopped (FALSE).

StartMode Start mode.

34


StatusDescriptions Strings describing the various OperationalStatus array value.

ECOM_RegisteredProfile

Table 3. Referenced Properties/Methods for ECOM_RegisteredProfile


InstanceID The unique identifier for the RegisteredProfile.

AdvertiseTypeDescription A free-form string providing additional information related to the AdvertiseType.

AdvertiseType Advertisement for the profile information.


Description The textual description of the object.

ElementName A use-friendly name of the object.

OtherRegisteredOrganization A free-form string providing additional description of the organization when {1: Other} is specified for the RegisteredOrganization.

RegisterName The name of the registered profile.

RegisteredOrganization The organization that defines the profile.

RegisteredVersion Version of the profile.

ECOM_System

Table 4. Referenced Properties/Methods for ECOM_System



Name A unique identifier of the CIM Server.




EnabledDefault Default or startup configuration for the EnabledState of the CIM Server.

EnabledState Enabled and disabled states of the CIM Server.

35


NameFormat The format of the Name property.


OtherEnabledState A string that describes the enabled or disabled state of the element when the EnabledState property is set to {1: Other}.




Roles An array of string that specifies the administrator-defined roles the CIM Server plays in the managed environment.


ECOM_Namespace

Table 5. Referenced Properties/Methods for ECOM_Namespcae




ObjectManagerCreationClassName CreationClassName of the scoping ObjectManager.

ObjectManagerName The name of the scoping ObjectManager.


Name A string that uniquely identifies the Namespace within the ObjectManager.


ClassType Schema of the objects in the Namespace.

ClassTypeVersion Version of the objects in the Namespace.


DescriptionOfClassType Detail for the object hierarchy of the namespace.

ElementName A user-friendly name.

ECOM_CIMXMLCommunicationMechanism

Table 6. Referenced Properties/Methods for ECOM_CIMXMLCommunicationMechanism

36






Name A string that uniquely identifies the access point.


AdvertiseType Advertisement for the access point.

AuthenticationMechanismDescriptions Description of the supported mechanism.

AuthenticationMechanismsSupported Types of authentication mechanism supported by the ObjectManager.

CIMValidated Whether the CIM Server is strictly validating or not.

CIMXMLProtocolVersion CIM-XML protocol version supported by the ObjectManager.

CommunicationMechanism The only valid mechanism for this subclass is CIM-XML.




EnabledDefault Default or startup configuration for the EnabledState of the ObjectManager.

EnabledState Enabled and disabled states of the ObjectManager.

FunctionalProfileDescriptions Descriptions of the operations supported by the ObjectManager using this protocol.

FunctionalProfilesSupport Types of operations supported by the ObjectManager using this protocol.

MultipleOperationsSupported Whether the ObjectManager supports multiple operation requests.


OtherCommunicationMechanismDescription

A free-form string providing additional description of the mechanism when {1: Other} is specified for the CommunicationMechanism.

OtherEnabledState A string that describes the enabled or disabled state of the

37


element when the EnabledState property is set to {1: Other}.



Version The CIM-XML version supported by the ObjectManager.


Table 7. Referenced Properties/Methods for ECOM_ElementConformsToProfile


ConformantStandard Reference of ECOM_RegisteredProfile

ManagedElement Reference of CIM_ManagedElement

ECOM_HostedService

Table 8. Referenced Properties/Methods for ECOM_HostedService


Antecedent Reference of ECOM_System

Dependent Reference of CIM_Service

38


Profile Registration Profile

Overview

In DMTF profiles, the term ‘component profile’ is similar to ‘subprofile’ used in SMI-S 1.0.x and 1.1.x; and the term ‘autonomous profile’ is similar to the ‘profile’ used in SMI-S 1.0.x and 1.1.x. SNIA implementations may use the SNIA 1.0.x/1.1.x approach with the RegisteredSubProfile and SubProfileRequiresProfile subclasses or the DMTF approach using RegisteredProfile for component profiles and ReferencedProfile.

SMI-S clients should use the superclasses (RegisteredProfile and ReferencedProfile) in CIM operations to assure that implementations conforming to either SMI-S or DMTF profiles are discovered. ReferencedProfile associates with two instances of RegisteredProfile. The DMTF Profile Registration Profile describes how the Antecedent and Dependent references should be used when one profile includes another in its supported/referenced profile list.

Instances of RegisteredProfile, RegisteredSubProfile, SubProfileRequiresProfile, and ReferencedProfile are in the Interop namespace. The ManagedElement is in the implementation namespace. RegisteredProfile instances are required by all SMI-S profiles, including those instances named as Subprofiles or Packages.

NOTE: For more details, refer to Clause 41: Profile Registration Profile in Storage Management Technical Specification, Part 2 Common Profiles, Version 1.5.0, Revision 6.

Class Diagram

Figure 3. Profile Registration Profile Class Diagram

39


Client Consideration

Version of SMI-S Profile

Each RegisteredProfile instance representing a profile from SMI-S version 1.2.0 or later (represented by ECOM_RegisteredSubProfile) is associated to a RegisteredProfile instance holding the SMI-S version number (represented by ECOM_RegisteredProfile). The version number (RegisteredVersion) of SMI-S profiles may or may not be the same as the version number of the SMI-S Registered Profile.

Note: For further information about how the client determines the version of an SMI-S profile,

refer to Use Case: Determine the SNIA Version of a SMI-S Profile.

Use Case: Using CIM server model to determine the supported SNIA Profiles

Client uses SLP discovery to determine the supported SNIA profiles.

For further information, refer to Clause 41: Profile Registration Profile in Storage Management Technical Specification, Part 2 Common Profiles, Version 1.5.0, Revision 6.

Use Case: Finding all profiles on a server

Invoking EnumerateInstances on CIM_RegisteredProfile, the client can get all profiles on CIM Server.

Use Case: Identifying the ManagedElement defined by a profile

From CIM_RegisteredProfile, traverse CIM_ElementConformsToProfile to CIM_ManagedElement to get all managed elements defined by the profile.

40


Use Case: Enumerating autonomous profiles supported by a given CIM server

A CIM_RegisteredProfile is an autonomous profile if the following conditions are satisfied:

Condition: The profile is not referenced by any other profiles.

Taking the current CIM_RegisteredProfile as a Dependent role, traverse CIM_ReferencedProfile to CIM_RegisteredProfile (role is Antecedent). If no result, the current profile is autonomous.

Use Case: Enumerate Autonomous Profiles

Determine Autonomy for a Profile

Find All Registered Profiles

Start

Connect to CIM Server EnumerateInstances of

CIM_RegisteredProfile in interop namespace

For each CIM_RegisteredProfile

Iteration Done

Traverse CIM_ReferencedProfile to CIM_RegisteredProfile(Antecedent)

Got Instance

Input CIM_RegisteredProfile

is autonomous


is not autonomous

N Y


N

Done

Y

Determination Done

Figure 4. Flowchart of Enumerating Autonomous Profiles

41


Use Case: Determine the SNIA version of a SMI-S Profile

This use case describes how to get the SNIA version information of an SMI-S Profile:

If the current profile is not associated with another CIM_RegisteredProfile (Role is ConformantStandard) via CIM_ElementConformsToProfile, use RegisteredVersion of current profile as the final version; otherwise, use RegisteredVersion of the resulting CIM_RegisteredProfile (ConformantStandard) as the final version.

Use Case: Determine SNIA Version of SMI-S ProfilePre-Condition: The profile to be processed was obtained previously

Determine SNIA Version of SMI-S Profile

Traverse CIM_ElementConformsToProfile to CIM_RegisteredProfile(ConformantStandard)

Got Instance

Extract RegisteredVersion of result CIM_RegisteredProfile

Y N


Final Version Determined

Extract RegisteredVersion of input CIM_RegisteredProfile

Figure 5. Flowchart of Determining SNIA Version of an SMI-S Profile

CIM Element

The implemented classes and associations related to the Profile Registration Profile in VNX File Storage System can be described as follows:

Table 9. CIM Elements for Profile Registration Profile


CIM_ElementConformsToProfile


Associates the RegisteredProfile for SMI-S autonomous profiles to scoping managed elements.

CIM_ReferencedProfile ECOM_ReferencedProfile Associates to a profile and its supported profiles.

CIM_RegisteredProfile ECOM_RegisteredProfile Registered profiles in ECOM including

42


autonomous profile and SMI-S Registered Profile.

CIM_RegisteredSubProfile ECOM_RegisteredSubProfile SMI-S Subprofile from version 1.2.0 or later.

CIM_SubProfileRequiresProfile

ECOM_SubProfileRequiresProfile

Specialization of ReferencedProfile referencing a SubProfile.

ECOM_RegisteredProfile

For further information, refer to ECOM_RegisteredProfile in Server Profile.

ECOM_RegisteredSubProfile

Table 10. Referenced Properties/Methods for ECOM_RegisteredSubProfile


InstanceID The unique identifier for the RegisteredProfile.


AdvertiseType Advertisement for the profile information.



ElementName A use-friendly name of the object.

OtherRegisteredOrganization A free-form string providing additional description of the organization when {1: Other} is specified for the RegisteredOrganization.

RegisterName The name of the registered profile.

RegisteredOrganization Organization that defines the profile.

RegisteredVersion Version of the profile.

ECOM_ReferencedProfile

Table 11. Referenced Properties/Methods for ECOM_ReferencedProfile


Antecedent Reference of ECOM_RegisteredProfile

Dependent Reference of ECOM_RegisteredProfile

43


ECOM_SubProfileRequiresProfile

Table 12. Referenced Properties/Methods for ECOM_SubProfileRequiresProfile


Antecedent Reference of ECOM_RegisteredProfile

Dependent Reference of ECOM_RegisteredSubProfile


For further information, refer to ECOM_ElementConformsToProfile in Server Profile.

44


NAS Head Profile

Overview

The NAS Head Profile exports file elements from a file system as file shares. The storage for the file system is obtained from external SAN storage; for example, a storage array that exports Storage Volumes as LUNs. The storage array may also provide storage to the other hosts or devices (or the other NAS Heads), and the storage on the array might be visible to the other external management tools, and may be managed actively and independently.

This profile models the necessary file system and NAS concepts, and defines how the connections to the underlying storage are managed.

The SMI-S Provider for VNX File Storage System implements the following subprofiles of the NAS Head Profile:

1. Multiple Computer System

2. File System

3. File Storage

4. File Export

5. Block Services (Read-only)

6. Extent Composition

7. Physical Package

8. Software

9. Location

10. Health Package

11. File System Manipulation (Read-only)

12. File Export Manipulation

13. NAS Network Port

14. Simple Identity Management (DSP1034)

NOTE: For more details, refer to Clause 13: NAS Head Profile in Storage Management Technical Specification, Part 4 Filesystems Version 1.6.0, Revision 4.

45


Class Diagram

Figure 6. NAS Head Class Diagram


System Hostname

Implemented in Celerra_CelerraComputerSystem.Name.

NFS Support

Virtual NFS File Server is only supported on Data Mover.

There can only be one Virtual NFS File Server hosted by one Data Mover.

46


Use Case: Discovering NAS Head

This use case describes how to discover NAS Head ComputerSystem and to retrieve LogicalDisk, StoragePool, and Virtual File Server of a VNX File Storage System:

Use Case: Discover NAS Head

Get LogicalDisk

Get StoragePool

Get Virtual File Server

Discover NAS Head ComputerSystem

Done

Y

Traverse CIM_SystemDevice to CIM_LogicalDisk

Traverse CIM_HostedPool to CIM_StoragePool

Traverse CIM_ComponentCS to CIM_ComputerSystem(PartComponent)

to get all component system

Traverse CIM_HostedDependency to CIM_ComputerSystem(Dependent)

{16:FileServer} in Dedicated

For each CIM_ComputerSystem(PartComponet)

For each CIM_ComputerSystem(Dependent)

Get next File Server

Y

N

Iteration done

N

Iteration done

N

Y

Start

Connect to CIM Server


interop namespace

Filter out CIM_RegisteredProfile instance for NAS Head Profile

Conditions: AdvertiseTypes is {3:SLP} and RegisteredName is {“NAS Head”}

Traverse CIM_ElementConformsToProfile

to CIM_ComputerSystem

Got instance

Y

Error

N

Got instance N

Y

NAS Head(Top-level) ComputerSystem

Get one File Server ComputerSystem

Figure 7. Flowchart of NAS Head Discovery

47


CIM Element

The implemented classes and associations related to the NAS Head profile in VNX File Storage System can be described as follows:

Table 13. CIM Elements for NAS Head Profile


CIM_ComponentCS

Celerra_ComponentCS_CCS_DMCS

Associates the Data Mover with the Top-level ComputerSystem.

Celerra_ComponentCS_CCS_VDMCS

Associates the Virtual Data Mover with the Top-level ComputerSystem.

CIM_ComputerSystem

Celerra_CelerraComputerSystem

Top-level Computer System (NAS Head ComputerSystem).

Celerra_DataMoverComputerSystem

Component ComputerSystem that represents Data Mover.

Celerra_VirtualDataMoverComputerSystem

Component ComputerSystem that represents Virtual Data Mover.

Celerra_NFSServer Virtual File Server that supports NFS protocol.

Celerra_CIFSServer Virtual File Server that supports CIFS protocol.

CIM_HostedDependency

Celerra_HostedDependency_DMCS_NFSS

Associates the Virtual NFS File Server with the Data Mover hosting it.

Celerra_HostedDependency_DMCS_CIFSS

Associates the Virtual CIFS File Server with the Data Mover hosting it.

Celerra_HostedDependency_VDMCS_CIFSS

Associates the Virtual CIFS File Server with the Virtual Data Mover hosting it.

CIM_LogicalDisk Celerra_LogicalDisk Meta Volume where a FileSystem can reside on.

CIM_StorageExtent Celerra_PrimordialStorageExtent

Disk Volume imported from VNX Block to File.

CIM_SystemDevice

Celerra_SystemDevice_CCS_LD

Links all LogicalDisk to the Top-level ComputerSystem.

Celerra_SystemDevice_CCS_PSE

Links all PrimordialStorageExtent to the Top-level ComputerSystem.

48



Table 14. Referenced Properties/Methods for Celerra_CelerraComputerSystem



Name Unique identifier for the NAS Head in a format specified by NameFormat.

Caption A user-friendly name preceded by the class name abbreviation.

Dedicated This shall be a NAS Head {24}.


IdentifyingDescriptions An array of descriptions of the OtherIdentifyingInfo.

NameFormat Format of the Name property.

OperationalStatus Overall status of the NAS Head.

OtherIdentifyingInfo An array of known identifiers for the NAS Head.




Table 15. Referenced Properties/Methods for Celerra_DataMoverComputerSystem


CreationClassName The name of class used to create this instance.

Name Unique identifier of the Data Mover.


Dedicated This shall be the other Computer System {0}.


NameFormat Format of the Name property.

OperationalStatus Overall status of the Data Mover.


Table 16. Referenced Properties/Methods for Celerra_VirtualDataMoverComputerSystem

49




Name Unique identifier of the Virtual Data Mover preceded with the System ID and Virtual Data Mover Name


Dedicated This shall be other Computer System {0}.


NameFormat Format of the Name property. The Value is set to {Other}.

OperationalStatus Overall status of the Virtual Data Mover.

Celerra_LogicalDisk

Table 17. Referenced Properties/Methods for Celerra_LogicalDisk


SystemCreationClassName CIM Class of the NAS Head Computer System that is the host of this LogicalDisk.

SystemName The name of the NAS Head Computer System that hosts this LogicalDisk.


DeviceID ID of the meta volume which can be used to build File system.

ElementName Name of the meta volume.

Name Name of the meta volume.

NameFormat The format of the Name appropriate for LogicalDisks in the NAS Head.

ExtentStatus Extent status.

OperationalStatus A subset of operational status that is applicable for LogicalDisks in a NAS Head.

BlockSize Block size of this element.

NumberOfBlocks The Number of blocks of this element.

ConsumableBlocks The number of blocks used by consumers.

IsBasedOnUnderlyingRedundancy Indicates whether or not underlying StorageExtent(s) participate in the StorageRedundancyGroup.

50



NoSinglePointOfFailure Indicates whether or not there is no single point of failure.

DataRedundancy The number of complete copies of data currently maintained.

PackageRedundancy Indicates the number of physical packages which allow real-time failure without data loss.

DeltaReservation The percentage that specifies the amount of space that should be reserved in a replica for caching changes.

Primordial Indicates whether or not the scoping system does not have the ability to create or delete this operational element.


Celerra_PrimordialStorageExtent

Table 18. Referenced Properties/Methods for Celerra_PrimordialStorageExtent


SystemCreationClassName The class Name of the scoping system (Top-level Computer System).



DeviceID ID of the disk volume.

ExtentStatus Extent status

OperationalStatus A subset of operational status that is applicable for StorageExtent in a NAS Head.


NumberOfBlocks Number of blocks of this element.

ConsumableBlocks The number of blocks used by consumers.


Name The name of the disk volume.

NameFormat The format of the Name appropriate for StorageExtent in the NAS Head.


51



ExtentDiscriminator Discriminator of this StorageExtent.

Celerra_NFSServer

Table 19. Referenced Properties/Methods for Celerra_NFSServer



Name The name of the Virtual File Server


Dedicated 16 indicates that this Computer System is a File Server

OperationalStatus Overall status of the Virtual File Server.



Celerra_CIFSServer

Table 20. Referenced Properties/Methods for Celerra_CIFSServer



Name The name of the Virtual File Server


Dedicated 16 indicates that this Computer System is a File Server

OperationalStatus Overall status of the Virtual File Server.




Table 21. Referenced Properties/Methods for Celerra_ComponentCS_CCS_DMCS


GroupComponent Reference of Celerra_CelerraComputerSystem

52


PartComponent Reference of Celerra_DataMoverComputerSystem


Table 22. Referenced Properties/Methods for Celerra_ComponentCS_CCS_VDMCS



PartComponent Reference of Celerra_VirtualDataMoverComputerSystem


Table 23. Referenced Properties/Methods for Celerra_SystemDevice_CCS_LD



PartComponent Reference of Celerra_LogicalDisk

Celerra_SystemDevice_CCS_PSE

Table 24. Referenced Properties/Methods for Celerra_SystemDevice_CCS_PSE



PartComponent Reference of Celerra_PrimordialStorageExtent


Table 25. Referenced Properties/Methods for Celerra_HostedDependency_DMCS_NFSS


Antecedent Reference of Celerra_DataMoverComputerSystem

Dependent Reference of Celerra_NFSServer


Table 26. Referenced Properties/Methods for Celerra_HostedDependency_DMCS_CIFSS


Antecedent Reference of Celerra_DataMoverComputerSystem

Dependent Reference of Celerra_CIFSServer

53



Table 27. Referenced Properties/Methods for Celerra_HostedDependency_VDMCS_CIFSS


Antecedent Reference of Celerra_VirtualDataMoverComputerSystem

Dependent Reference of Celerra_CIFSServer

54


Block Services Package

Overview

Block Service Package in VNX SMI-S Provider is a read-only implementation. None of the extrinsic methods of Block Service are supported since the implementation does not provide any instance of StorageConfigurationService.

This profile only defines a standard expression of existing storage capacity, the assignment of capacity to StoragePools, and the allocation of capacity is to be done by the CLI, GUI, or other non SMI-S application.

NOTE: For more details, refer to Clause 5: Block Services Package in Storage Management Technical Specification, Part 3 Block Devices, Version 1.6.0, Revision 4.

Class Diagram

Figure 8. Block Service Class Diagram

55



Storage Manipulation

Any block service manipulation from SMI-S Provider is not supported since the profile is Read-Only implemented.

StoragePool Usage

StoragePool.Usage indicates the intended usage of the StoragePool.

StoragePool OperationalStatus

Value is set to {2: OK} for Primordial and Concrete pools.

Celerra_PrimordialStoragePool

There must be one and only one instance of Celerra_PrimordialStoragePool.

Celerra_NonPrimordialStoragePool

Concrete pool used to create LocalFileSystem. There can be one or more NonPrimordialStoragePools which are allocated from the PrimordialStoragePool.

System Total Storage Capacity

Implemented in Celerra_PrimordialStoragePool.TotalManagedSpace.

System Remaining Available Storage Capacity

Implemented in Celerra_PrimordialStoragePool.RemaningManagedSpace.

Concrete Pool Total Storage Capacity

Implemented in Celerra_NonPrimordialStoragePool.TotalManagedSpace.

Concrete Pool Remaining Available Storage Capacity

Implemented in Celerra_NonPrimordialStoragePool.RemaningManagedSpace.

56


Use Case: Summarizing StoragePools and Verifying reported Capacity

The value of StoragePool.RemainingManagedSpace plus all spaces consumed by each element allocated from the StoragePool in AllocatedFromStoragePool.SpaceComsumed should be equal to the value of StoragePool.TotalManagedSpace.

Use Case: Summarize StoragePools and Verify Reported CapacityPre-Condition: StoragePools were obtained previously.

Verify Reported Capacity for a StoragePool

Get StoragePools

Get StoragePools(refer to case NAS Head Profile)

For each CIM_StoragePool

Iteration Done

Reference CIM_AllocatedFromStoragePool (Role is Antecedent)

Input CIM_StoragePool

N

Done

Verification Done

Set variables Total = CIM_StoragePool.TotalManagedSpace Remaining = CIM_StoragePool.RemainingManagedSpace Consumed = 0

For each CIM_AllocatedFromStoragePool related to input CIM_StoragePool(Antecedent)

Iteration Done

Consumed = Consumed + CIM_AllocatedFromStoragePool.SpaceConsumed

Consumed space calculated

N

Y

Total == Remaining + Consumed

Verification Passed Verification Failed

Y N

Y

Figure 9. Flowchart of StoragePool Summary and Capacity Verification

57


CIM Element

The implemented classes and associations related to the Block Service Package in VNX File Storage System can be described as follows:

Table 28. CIM Elements for Block Service Package


CIM_AllocatedFromStoragePool

Celerra_AllocatedFromStoragePool_PSP_NPSP

Links NonPrimordialStoragePool to PrimordialStoragePool where it is allocated from.

Celerra_AllocatedFromStoragePool_NPSP_LD

Links LogicalDisk to NonPrimordialStoragePool where it is allocated from.

CIM_HostedStoragePool

Celerra_HostedStoragePool_CCS_PSP

Links PrimordialStoragePool to its scoping system (Top-level ComputerSystem).

Celerra_HostedStoragePool_CCS_NPSP

Links NonPrimordialStoragePool to its scoping system (Top-level ComputerSystem).

CIM_LogicalDisk Celerra_LogicalDisk Meta Volume where a FileSystem can reside on.

CIM_StorageCapabilities Celerra_StoragePoolStorageCapabilities

Capabilities of a StoragePool(Primordial or Concrete pool)

CIM_StoragePool


Collection of imported disk volumes from VNX Block to File.


Concrete StoragePool (e.g. System/User defined storage pool)

CIM_StorageSetting Celerra_LogicalDiskStorageSetting

StorageSetting for a LogicalDisk

CIM_SystemDevice Celerra_SystemDevice_CCS_LD

Links LogicalDisk to its scoping system (Top-level ComputerSystem).


Table 29. Referenced Properties/Methods for Celerra_PrimordialStoragePool


InstanceID The unique identifier for the StoragePool.

Primordial Indicates whether the StoragePool is primordial or not.

58


PoolID A unique name in the context of the system that identifies this StoragePool.

TotalManagedSpace The total amount of capacity.

RemainingManagedSpace The remaining usable capacity.



OperationalStatus Current status of the StoragePool.

Usage Indicates the intended usage or any restrictions may have been imposed on the usage of this object.

HealthState Current health of the StoragePool.


Table 30. Referenced Properties/Methods for Celerra_NonPrimordialStoragePool


InstanceID The unique identifier for the StoragePool.

Primordial Indicates whether the StoragePool is primordial or not.

PoolID A unique name in the context of the system that identifies this StoragePool.

TotalManagedSpace The total amount of capacity.

RemainingManagedSpace The remaining usable capacity.


OperationalStatus Current status of the StoragePool.

Usage Indicates the intended usage or any restrictions may have been imposed on the usage of this object.

HealthState Current health of the StoragePool.

Celerra_LogicalDisk

For further information, refer to Celerra_LogicalDisk in NAS Head Profile.

Celerra_StoragePoolStorageCapabilities

Table 31. Referenced Properties/Methods for Celerra_StoragePoolStorageCapabilities


59


InstanceID The unique identifier for this storage pool capability.

ElementName A user-friendly name of this instance.

ElementType Type of element to which this StorageCapabilities applies.

NoSinglePointOfFailure Whether or not the associated element supports no single point of failure.

NoSinglePointOfFailureDefault Default value of NoSinglePointOfFailure.

DataRedundancyMin The minimum number of complete copies of data that can be maintained.

DataRedundancyMax The maximum number of complete copies of data that can be maintained.

DataRedundancyDefault The default number of complete copies of data that can be maintained.

PackageRedundancyMin The minimum number of redundant packages that can be used.

PackageRedundancyMax The maximum number of redundant packages that can be used.

PackageRedundancyDefault The default number of redundant packages that can be used.


ParityLayoutDefault Whether a parity-based storage organization is using rotated or non-rotated parity.

Celerra_LogicalDiskStorageSetting

Table 32. Referenced Properties/Methods for Celerra_LogicalDiskStorageSetting


InstanceID The unique identifier for this storage pool capability.


ChangeableType Changeable type of setting.

DataRedundancyMin The minimum number of complete copies of data that can be maintained.

DataRedundancyMax The maximum number of complete copies of data that can be maintained.

DataRedundancyGoal The desired number of complete copies of data that can be maintained.

ElementName User-friendly name of this instance.

60


ExtentStripeLength The number of underlying StorageExtent across which data is striped in the common striping-based storage organization.

ExtentStripeLengthMax The maximum number of underlying StorageExtent across which data is striped in the common striping-based storage organization.

ExtentStripeLengthMin The minimal number of underlying StorageExtent across which data is striped in the common striping-based storage organization.

NoSinglePointOfFailure Whether or not the associated element supports no single point of failure.

PackageRedundancyMin The minimum number of redundant packages that can be used.

PackageRedundancyMax The maximum number of redundant packages that can be used.

PackageRedundancyDefault The default number of redundant packages that can be used.

ParityLayoutDefault Whether a parity-based storage organization is using rotated or non-rotated parity.

StorageExtentInitialUsage The Usage value to be used when creating a new element that is derived from a StorageExtent.

StoragePoolInitialUsage The Usage value to be used when creating a new StoragePool.

UserDataStripeDepth The number of bytes forming a strip in common striping-based storage organization.

UserDataStripeDepthMax The maximum number of bytes forming a strip in common striping-based storage organization.

UserDataStripeDepthMin The minimum number of bytes forming a strip in common striping-based storage organization.

Celerra_HostedStoragePool_CCS_PSP

Table 33. Referenced Properties/Methods for Celerra_HostedStoragePool_CCS_PSP



PartComponent Reference of Celerra_PrimordialStoragePool

Celerra_HostedStoragePool_CCS_NPSP

Table 34. Referenced Properties/Methods for Celerra_HostedStoragePool_CCS_NPSP


61



PartComponent Reference of Celerra_NonPrimordialStoragePool

Celerra_AllocatedFromStoragePool_PSP_NPSP

Table 35. Referenced Properties/Methods for Celerra_AllocatedFromStoragePool_PSP_NPSP


Antecedent Reference of Celerra_PrimordialStoragePool

Dependent Reference of Celerra_NonPrimordialStoragePool

Celerra_AllocatedFromStoragePool_NPSP_LD

Table 36. Referenced Properties/Methods for Celerra_AllocatedFromStoragePool_NPSP_LD


Antecedent Reference of Celerra_NonPrimordialStoragePool

Dependent Reference of Celerra_LogicalDisk


For further information, refer to Celerra_SystemDevice_CCS_LD in NAS Head Profile.

62


File System Profile

Overview

The FileSystem Profile is a subprofile for autonomous profiles that support file systems. Specifically, for SMI-S v1.6, this includes the NAS Head and the Self-Contained NAS Profiles.

A number of other profiles and subprofiles make use of elements of the FileSystem Profile. These include but are not limited to the FileSystem Manipulation Subprofile, File Export Subprofile, File Export Manipulation Subprofile, NAS Head Profile, etc.

NOTE: For more details, refer to Clause 8: FileSystem Profile in Storage Management Technical Specification, Part 4 Filesystems Version 1.6.0, Revision 4.

Class Diagram

Figure 10. File System Class Diagram

63



FileSystem Type

Only user-defined UXFS file systems are exposed to client by SMI-S Provider in class Celerra_UxfsLocalFileSystem.

Vital Information of FileSystem

The following vital information is provided in Celerra_UxfsLocalFileSystem:

Table 6. Vital Information of FileSystem

Property Name Description

Name FileSystem ID.

ElementName Readable FileSystem name.

FileSystemType Type of the FileSystem.

Value is set to EMC_UXFS.

FileSystemSize Total size of the FileSystem.

AvailableSpace Remaining available space of the FileSystem.

NumberOfFiles

Used to indicate whether there are files in the FileSystem.

Value will be set to

{1} – There are files in the FileSystem

{0} – There is no file in the FileSystem

{Maximum of UINT_64} – Error occurred when retrieving this property from backend component.

CaseSensitive Whether the FileSystem is case sensitive in file names.

The value is set to {True}.

MaxFileNameLength

The length of the longest file name supported in implementation.

The value is set to {255}.

LocalAccessDefinitionRequired

Used to indicate whether provider requires that a file system device to be made locally accessible before it can be used as a file system.

The value is set to {3: Required – vendor default}.

OperationalStatus

The current operational status of the FileSystem.

The value will be set to:

{2:OK} -- the FileSystem is mounted to a Data Mover or Virtual Data Mover

{11:In Service} -- the FileSystem is not mounted to any Data Mover or Virtual Data Mover

{13: Lost Communication} – SMI-S Provider can not retrieve operational status due to some certain communication error in backend system.

64


FileSystem Size and Available Space

Client can retrieve FileSystem total size and remaining available space if (and only if) Celerra_UxfsLocalFileSystem.OperationalStatus is {2: OK}. That is, the FileSystem must be mounted to a Data Mover or Virtual Data Mover.

Make FileSystem Locally Accessible

Mounting a FileSystem to a Data Mover or Virtual Data Mover enables the FileSystem to be locally accessible for all Virtual File Servers hosted by the Data Mover or Virtual Data Mover.

FileSystem Access Path

Implemented in Celerra_LocalAccessAvailable_CIFSS_UFS.LocalAccessPoint and Celerra_LocalAccessAvailable_NFSS_UFS.LocalAccessPoint.

This property specifies the name used by the FileServer to identify the FileSystem.

FileSystem Read Write Policy

Implemented in Celerra_LocallyAccessibleFileSystemSetting.ReadWritePolicy.

Use Case: Listing existing file systems hosted by the referencing profile

From file system host (NAS Head ComputerSystem), traverse CIM_HostedFileSystem to SNIA_LocalFileSystem (inherited from CIM_LocalFileSystem) to list all the existing file systems.

Use Case: Getting FileSystemSettings for a file system

From the FileSystem, traverse CIM_ElementSettingData to CIM_FileSystemSetting to obtain the setting information for the FileSystem.

Use Case: Getting the ComputerSystem that hosts a file system

From the FileSystem, traverse CIM_HostedFileSystem to CIM_ComputerSystem to obtain the system that hosts the FileSystem.

Use Case: Getting all file servers and access paths that have local access to this file system

From the FileSystem, reference SNIA_LocalAccessAvailable.

FileServer that has local access ability to the FileSystem is represented by SNIA_LocalAccessAvailable.FileServer and Access path is indicated by SNIA_LocalAccessAvailable.LocalAccessPoint.

Use Case: Getting the access path to a given file system on the specified file server

Using the specified FileServer as a filter, filter out required entry from the result of Use Case: Get all file servers and access paths that have local access to this file system.

Use Case: Getting the Local Access Settings for a given file system on the specified fileserver

From the FileSystem, traverse CIM_ElementSettingData to SNIA_LocallyAccessibleFileSystemSetting to get all local access settings associated to the file system.

For each SNIA_LocallyAccessibleFileSystemSetting, traverse CIM_HostedDependency to CIM_ComputerSystem (File Server) to get the FileServer. If the FileServer is the one specified, return

65


current SNIA_LocallyAccessibleFileSystemSetting as the result; otherwise, check the next instance of SNIA_LocallyAccessibleFileSystemSetting.

Use Case: Getting the FileShares of a given file system on all file servers

From the FileSystem, traverse CIM_SharedElement to CIM_FileShare to get all FileShare of the FileSystem on all FileServers.

Use Case: Getting the FileShares of a given file system on the specified file server

From the FileSystem, traverse CIM_SharedElement to CIM_FileShare to get all File Share of the FileSystem on all FileServers.

For each FileShare, traverse CIM_HostedShare to CIM_ComputerSystem to get FileServer that hosts the share. If the FileServer is the one specified, add current FileShare into the result; otherwise, check next FileShare.

CIM Element

The implemented classes and associations related to the File System Profile in VNX File Storage System can be described as follows:

Table 37. CIM Elements for File System Profile


CIM_ElementSettingData

Celerra_ElementSettingData_UFS_FSS

Associates configuration settings with LocalFileSystem.

Celerra_ElementSettingData_UFS_LAFSS

Associates locally accessible configuration settings with LocalFileSystem.


Celerra_HostedDependency_CIFSS_LAFSS

Associates locally accessible configuration settings with the virtual CIFS File Server that can locally access the FileSystem.

Celerra_HostedDependency_NFSS_LAFSS

Associates locally accessible configuration settings with the virtual NFS File Server that can locally access the FileSystem.

CIM_HostedFileSystem Celerra_HostedFileSystem_CCS_UFS

Associates LocalFileSystem with the File Host (NAS Head ComputerSystem).

SNIA_LocalFileSystem Celerra_UxfsLocalFileSystem UXFS FileSystem defined by clients.

SNIA_FileSystemSetting Celerra_FileSystemSetting Configuration settings of a UXFS FileSystem.

SNIA_LocalAccessAvailable Celerra_LocalAccessAvailable_CIFSS_UFS

Associates LocalFileSystem with the virtual CIFS File Server that can locally

66


access the FileSystem.

Celerra_LocalAccessAvailable_NFSS_UFS

Associates LocalFileSystem with the virtual NFS File Server that can locally access the FileSystem.

SNIA_LocallyAccessibleFileSystemSetting

Celerra_LocallyAccessibleFileSystemSetting

This element represents the configuration settings of a LocalFileSystem that can be made locally accessible from a File Server ComputerSystem. This setting provides further details on the functionality supported and the parameters of that functionality when locally accessible.

Celerra_UxfsLocalFileSystem

Table 38. Referenced Properties/Methods for Celerra_UxfsLocalFileSystem


CSCreationClassName CIM Class of the Computer System that is the host of this FileSystem.

SystemName The name of the Computer System that hosts this FileSystem.


Name Unique identifier of this element.

ElementName Readable FileSystem name.

FileSystemType Type of the FileSystem.

FileSystemSize Total capacity of the FileSystem.

AvailableSpace Remaining usable capacity of the FileSystem.

NumberOfFiles The number of the files in the FileSystem.

CaseSensitive Whether the FileSystem is case sensitive in file names.

CasePreserved Whether the FileSystem implementation preserves the case of characters in file name when saving and restoring.

MaxFileNameLength The length of the longest file name supported in the implementation.

LocalAccessDefinitionRequired Whether the provider requires that a file system device to be made locally accessible before it can be used as a FileSystem.

OperationalStatus Current operational status of the FileSystem.

67


PathNameSeparatorString Separator of the path in the FileSystem.

LocalAccessDefinitionRequired Required type of local access definition.


Celerra_FileSystemSetting

Table 39. Referenced Properties/Methods for Celerra_FileSystemSetting


InstanceID The unique identifier for this instance.



ActualFileSystemType Type of the FileSystem that this setting represents.

FilenameCaseAttributes Specifies the support of using upper and lower case characters in file name.

NumberOfObjects An array that specifies the expected number of objects of the type specified by the corresponding entry in ObjectTypes.

NumberOfObjectsMax An array that specifies the maximum expected number of objects of the type specified by the corresponding entry in ObjectTypes.

NumberOfObjectsMin An array that specifies the minimum number of objects of the type specified by the corresponding entry in ObjectTypes.

ObjectTypes An array that specifies different types of objects that this FileSystem may be used to provide and provides further details in corresponding entries in other attributes.

ObjectSizeMax An array that specifies the maximum size of an object of the type specified by the corresponding entry in ObjectTypes.

ObjectSizeMin An array that specifies the minimum size of an object of the type specified by the corresponding entry in ObjectTypes.

Celerra_LocallyAccessibleFileSystemSetting

Table 40. Referenced Properties/Methods for Celerra_LocallyAccessibleFileSystemSetting


InstanceID The unique identifier for this instance.


68


ReadWritePolicy The Read-Write policy set on the operational FileSystem and supported by the operational FileServer when accessing it.

Celerra_HostedFileSystem_CCS_UFS

Table 41. Referenced Properties/Methods for Celerra_HostedFileSystem_CCS_UFS



PartComponent Reference of Celerra_UxfsLocalFileSystem

Celerra_LocalAccessAvailable_NFSS_UFS

Table 42. Referenced Properties/Methods for Celerra_LocalAccessAvailable_NFS_UFS


FileServer Reference of Celerra_NFSServer

FileSystem Reference of Celerra_UxfsLocalFileSystem

LocalAccessPoint Mountpoint of the FileSystem

Celerra_LocalAccessAvailable_CIFSS_UFS

Table 43. Referenced Properties/Methods for Celerra_LocalAccessAvailable_CIFS_UFS


FileServer Reference of Celerra_NFSServer

FileSystem Reference of Celerra_UxfsLocalFileSystem

LocalAccessPoint Mountpoint of the FileSystem

Celerra_ElementSettingData_UFS_FSS

Table 44. Referenced Properties/Methods for Celerra_ElementSettingData_UFS_FSS


ManagedElement Reference of Celerra_UxfsLocalFileSystem

SettingData Reference of Celerra_FileSystemSetting

Celerra_ElementSettingData_UFS_LAFSS

Table 45. Referenced Properties/Methods for Celerra_ElementSettingData_UFS_LAFSS


69


ManagedElement Reference of Celerra_UxfsLocalFileSystem

SettingData Reference of Celerra_LocalAccessibleFileSystemSetting

Celerra_HostedDependency_NFSS_LAFSS

Table 46. Referenced Properties/Methods for Celerra_HostedDependency_NFS_LAFSS


Antecedent Reference of Celerra_NFSServer

Dependent Reference of Celerra_LocalAccessibleFileSystemSetting

Celerra_HostedDependency_CIFSS_LAFSS

Table 47. Referenced Properties/Methods for Celerra_HostedDependency_CIFS_LAFSS


Antecedent Reference of Celerra_CIFSServer

Dependent Reference of Celerra_LocalAccessibleFileSystemSetting

70


File Storage Profile

Overview

The File Storage Profile models the mapping of FileSystems to LogicalDisks. For the NAS Head and Self-contained NAS Profiles, each FileSystem shall be established on one LogicalDisk. The relationship between the LocalFileSystem and the LogicalDisk is represented by the ResidesOnExtent association.

The FileStorage Profile is a “read-only” profile. That is, the methods for creating, modifying or deleting a LocalFileSystem are external to the File Storage Profile. The SMI-S prescribed way of performing these functions are covered by the File System Manipulation Profile.

NOTE: For more details, refer to Clause 7: File Storage Profile in Storage Management Technical Specification, Part 4 Filesystems Version 1.6.0, Revision 4.

Class Diagram

Figure 11. File Storage Class Diagram


N/A

71


CIM Element

The implemented classes and associations related to the File Storage Profile in VNX File Storage System can be described as follows:

Table 48. CIM Elements for File Storage Profile


CIM_ResidesOnExtent Celerra_ResidesOnExtent_LD_UFS

Associates the LocalFileSystem with LogicalDisk where the Filesystem can reside on.

Celerra_ResidesOnExtent_LD_UFS

Table 49. Referenced Properties/Methods for Celerra_ResidesOnExtent_LD_UFS


Antecedent Reference of Celerra_LogicalDisk

Dependent Reference of Celerra_UxfsLocalFileSystem

72


File Export Profile

Overview

The File Export Profile is a subprofile for autonomous profiles that support exporting of file systems. Specifically, in this release of SMI-S, it is the NAS Head Profile.

NOTE: For more details, refer to Clause 4: File Export Profile in Storage Management Technical Specification, Part 4 Filesystems Version 1.6.0, Revision 4.

Class Diagram

Figure 12. File Export Class Diagram

73



File Share Enumeration

The following shares are not exposed to the client in SMI-S Provider:

Global share

Share exported from FileSystem of which the type is not UXFS.

Exported File Share Setting

The following vital information is provided in Celerra_ExportedFileShareSetting:

Table 50. Vital Information of File Share Setting

Property Name Description

FileSharingProtocol File sharing protocol supported by the File Share.

Supported values are {2:NFS, 3:CIFS}

ProtocolVersions An array of version strings of the supported File Sharing Protocol.

DefaultReadWrite

Default privilege for read-write authorization.

Supported values are {2:No Access, 3:Read Only, 4:Read/Write}

CASupported Specifies whether Continuous Availability (CA) was supported by the File Share.

AccessPoints

Specifies the service access points that are available to this File Share by default.

The value will be set to {5: Named Points}

DefaultUserIdSupported

Specifies whether the File Share will use a default user ID to control access if the ID of the imported client is not provided.

The value will be set to {2: No Default User Id}

RootAccess

Specifies whether the File Share supports default access by privileged, system administrator- level (root) users from specific hosts.

The value will be set to {3: Allow Root Access}

Associations with File Share

The cardinality between the FileShare and FileServer via HostedShare is many-to-one. Zero or more FileShares may be hosted by one FileServer. But each FileShare shall only be hosted by one FileServer.

The cardinality between the FileShare and ProtocolEndpoint via SAPAvailableForElement is many-to-many. That is, multiple FileShares may be exported through the same ProtocolEndpoint and multiple ProtocolEndpoints may support the same FileShare.

The cardinality between the FileShare and LocalFileSystem via SharedElement is many-to-one. Zero or more FileShares may be associated with one LocalFileSystem. But each FileShare shall only reference one LocalFileSystem.

74


Use Case: Listing existing FileShares on the system

From the File Server ComputerSystem, traverse CIM_HostedShare to CIM_FileShare to list all shares on the File Server.

CIM Element

The implemented classes and associations related to the File Export Profile in VNX File Storage System can be described as follows:

Table 51. CIM Elements for File Export Profile


CIM_ElementSettingData

Celerra_ElementSettingData (File Share)

Celerra_ElementSettingData_EFSS_NFSFS

Celerra_ElementSettingData_EFSS_CIFSFS

Associates File Share (NFS or CIFS) with its exported configuration settings.

CIM_SAPAvailableForElement

Celerra_SAPAvailableForElement_CIFSFS_CIFSPE

Celerra_SAPAvailableForElement_NFSFS_NFSPE

Associates the File Share (NFS or CIFS) with the ProtocolEndpoint through which the File Share is being accessed.

CIM_SharedElement

Celerra_SharedElement

Celerra_SharedElement_NFSFS_UFS

Celerra_SharedElement_CIFSFS_UFS

Associates the File Share (NFS or CIFS) with the LocalFileSystem on which it is based.

SNIA_CIFSShare Celerra_CIFSShare A File Share exported by CIFS protocol.

SNIA_ExportedFileShareSetting

Celerra_ExportedFileShareSetting (for File Share)

Configuration settings for an exported File Share.

SNIA_HostedShare

Celerra_HostedShare_NFSFS_NFSS

Celerra_HostedShare_CIFSFS_CIFSS

Associates File Share (NFS or CIFS) with its scoping File Server.

SNIA_NFSShare Celerra_NFSShare A File Share exported by NFS protocol.

Celerra_NFSShare

Table 52. Referenced Properties/Methods for Celerra_NFSShare


75


InstanceID A unique string identifying the NFS share.

Caption The short textual description of the NFS share.

ElementName A user-friendly name of the NFS share.

Name The name of the NFS share.

OperationalStatus Current status of the NFS share.

PathNameSeparatorString The string that separates the path name.

SharingDirectory Indicates if the shared element is a file or a directory.

Celerra_CIFSShare

Table 53. Referenced Properties/Methods for Celerra_CIFSShare


InstanceID A unique string identifying the CIFS share.

Caption The short textual description of the CIFS share.

ElementName A user-friendly name of the CIFS share.

Name The name of the CIFS share.

OperationalStatus Current status of the CIFS share.

PathNameSeparatorString The string that separates the path name.

SharingDirectory Indicates if the shared element is a file or a directory.

Celerra_ExportedFileShareSetting

Table 54. Referenced Properties/Methods for Celerra_ExportedFileShareSetting


InstanceID A unique string identifying the instance.

Caption The short textual description of the CIFS share.

ElementName A user-friendly name of the CIFS share.

FileSharingProtocol File sharing protocol supported by the File Share.

ProtocolVersions An array of version strings of the supported File Sharing Protocol.

DefaultReadWrite Default privilege for read-write authorization.

76


CASupported Specifies whether Continuous Availability (CA) is supported by the File Share.

AccessPoints Specifies the service access points that are available to this File Share by default.

DefaultUserIdSupported Specifies whether the File Share will use a default user ID to control access if the ID of the importing client is not provided.

RootAccess Specifies whether the File Share supports default access by privileged, users of system administrator level (root) from specific hosts.

InitialEnabledState The enabled/disabled states initially set for a File Share.

Celerra_HostedShare_NFSFS_NFSS

Table 55. Referenced Properties/Methods for Celerra_HostedShare_NFSFS_NFSS



Dependent Reference of Celerra_NFSShare

Celerra_HostedShare_CIFSFS_CIFSS

Table 56. Referenced Properties/Methods for Celerra_HostedShare_CIFSFS_CIFSS



Dependent Reference of Celerra_CIFSShare

Celerra_ElementSettingData_EFSS_NFSFS

Table 57. Referenced Properties/Methods for Celerra_ElementSettingData_EFSS_NFSFS


SettingData Reference of Celerra_ExportedFileShareSetting

ManagedElement Reference of Celerra_NFSShare

Celerra_ElementSettingData_EFSS_CIFSFS

Table 58. Referenced Properties/Methods for Celerra_ElementSettingData_EFSS_CIFSFS


SettingData Reference of Celerra_ExportedFileShareSetting

77


ManagedElement Reference of Celerra_CIFSShare

Celerra_SAPAvailableForElement_NFSFS_NFSPE

Table 59. Referenced Properties/Methods for Celerra_SAPAvailableForElement_NFSFS_NFSPE


AvailableSAP Reference of Celerra_NFSProtocolEndpoint

ManagedElement Reference of Celerra_NFSShare

Celerra_SAPAvailableForElement_CIFSFS_CIFSPE

Table 60. Referenced Properties/Methods for Celerra_SAPAvailableForElement_CIFSFS_CIFSPE


AvailableSAP Reference of Celerra_CIFSProtocolEndpoint

ManagedElement Reference of Celerra_CIFSShare

Celerra_SharedElement_NFSFS_UFS

Table 61. Referenced Properties/Methods for Celerra_SharedElement_NFSFS_UFS


SameElement Reference of Celerra_NFSShare

SystemElement Reference of Celerra_UxfsLocalFileSystem

Celerra_SharedElement_CIFSFS_UFS

Table 62. Referenced Properties/Methods for Celerra_SharedElement_CIFSFS_UFS


SameElement Reference of Celerra_CIFSShare

SystemElement Reference of Celerra_UxfsLocalFileSystem

78


NAS Network Port Profile

Overview

The NAS Network Port Profile models the ProtocolEndpoints for file access (CIFS and NFS), TCP and IP. It also models the Network Port supported by the protocol endpoints. This profile provides basic information in the NAS models for addressing paths for accessing the NAS implementations in the purpose of data access (front-end ports).

The methods for manipulating these elements are not supported by VNX SMI-S Provider.

NOTE: For more details, refer to Clause 15: NAS Network Port Profile in Storage Management Technical Specification, Part 4 Filesystems Version 1.6.0, Revision 4.

Class Diagram

Figure 13. NAS Network Class Diagram


NAS Network Port Manipulation

None of the network port element manipulation is provided by SMI-S Provider.

EthernetPort Enumeration

Only Ethernet devices in types of ace, fge, cge, cxg and fxg are exposed to client by SMI-S Provider.

Table 63. Data Mover Interface Name Format

79


Prefix Link Type

a - PCI attached network card f - Fiber c - Copper m - Management

ge – Gigabits Ethernet xg – 10 Gigabits Ethernet

HostAccessPoint

The association between ProtocolEndpoint and File Sever does not exist in case that there is no IP interface assigned to the File Server.

CIM Element

The implemented classes and associations related to the NAS Network Port in VNX File Storage System can be described as follows:

Table 64. CIM Elements for NAS Network Port


CIM_BindsTo

Celerra_BindsTo

Celerra_BindsTo_TCPPE_CIFSPE

Celerra_BindsTo_TCPPE_NFSPE

Celerra_BindsTo_IPPE_TCPPE

Associates upper-level ProtocolEndpoint with the underlying ProtocolEndpoint. E.g. CIFS or NFS to TCP and TCP to IP

CIM_DeviceSAPImplementation

Celerra_DeviceSAPImplementation

Celerra_DeviceSAPImplementation_DMEP_IPPE

Celerra_DeviceSAPImplementation_DMEP_CIFSPE

Celerra_DeviceSAPImplementation_DMEP_NFSPE

Associates a CIFS, NFS or IP ProtocolEndpoint with the NetworkPort that supports the ProtocolEndpoint.

CIM_ElementSettingData Celerra_ElementSettingData_IPPE_IPISD

Associates IPInterfaceSettingData with IPProtocolEndpoint.

CIM_EthernetPort Celerra_DMEthernetPort Ethernet device port on Data Mover/Virtual Data Mover.

CIM_HostedAccessPoint

Celerra_HostedAccessPoint

Celerra_HostedAccessPoint_CIFSS_CIFSPE

Celerra_HostedAccessPoint_CIFSS_TCPPE

Celerra_HostedAccessPointCIFSS_IPPE

Associates ProtocolEndpoint (CIFS, NFS, TCP, IP) with its scoping ComputerSystem (the Virtual File Server).

80


Celerra_HostedAccessPoint_NFSS_NFSPE

Celerra_HostedAccessPoint_NFSS_TCPPE

Celerra_HostedAccessPoint_NFSS_IPPE

CIM_ProtocolEndpoint

Celerra_CIFSProtocolEndpoint

Front-End protocol endpoint for CIFS service.

Celerra_NFSProtocolEndpoint

Front-End protocol endpoint for NFS service.

Celerra_TCPProtocolEndpoint

Front-End protocol endpoint for TCP service.

Celerra_IPProtocolEndpoint Front-End protocol endpoint for IP service.

CIM_SystemDevice

Celerra_SystemDevice (for EthernetPort)

Celerra_SystemDevice_DMCS_DMPE

Celerra_SystemDeviceVDMCS_DMPE

Associates Ethernet device port with its scoping ComputerSystem (Data Mover/Virtual Data Mover).

SNIA_IPInterfaceSettingData Celerra_IPInterfaceSettingData

Settings for single interface.

Celerra_DMEthernetPort

Table 65. Referenced Properties/Methods for Celerra_DMEthernetPort


SystemCreationClassName The class name of scoping system.



DeviceID A unique identifier for the Ethernet Port in context of the hosting system.


ElementName A user-friendly name of the Ethernet Port.

NetworkAddress An array of network address for this port.

PermanentAddress MAC address of this port.

81



OperationalStatus Current status of this port.

Celerra_CIFSProtocolEndpoint

Table 66. Referenced Properties/Methods for Celerra_CIFSProtocolEndpoint





Name A unique identifier for the CIFS Protocol Endpoint.


Description The textual description of the protocol endpoint.


ProtocolIFType Interface type for this protocol endpoint.

OperationalStatus Current status of this protocol endpoint.

Celerra_NFSProtocolEndpoint

Table 67. Referenced Properties/Methods for Celerra_NFSProtocolEndpoint





Name A unique identifier for the NFS Protocol Endpoint.






82


Celerra_TCPProtocolEndpoint

Table 68. Referenced Properties/Methods for Celerra_TCPProtocolEndpoint





Name A unique identifier for the TCP Protocol Endpoint.

PortNumber The TCP port number.





Celerra_IPProtocolEndpoint

Table 69. Referenced Properties/Methods for Celerra_IPProtocolEndpoint





Name A unique identifier for the TCP Protocol Endpoint.

IPv4Address The IPv4 address for this protocol endpoint.





Celerra_IPInterfaceSettingData

Table 70. Referenced Properties/Methods for Celerra_IPInterfaceSettingData


83



InstanceID A unique identifier of this instance.

AddressType Format of the IP address.

IPAddress The IP address that this IP Interface represents.

LinkSpeed Link speed of this interface.

IPv4Address The IPv4 address for this protocol endpoint.

RDMACapable Whether RDMA capable or not.

RSSCapable Whether RSS capable or not.

SubnetMask The mask for the IP address.

Celerra_ElementSettingData_IPPE_IPISD

Table 71. Referenced Properties/Methods for Celerra_ElementSettingData_IPPE_IPISD


SettingData Reference of Celerra_IPInterfaceSettingData

ManagedElement Reference of Celerra_IPProtocolEndpoint

Celerra_HostedAccessPoint_CIFSS_CIFSPE

Table 72. Referenced Properties/Methods for Celerra_HostedAccessPoint_CIFSS_CIFSPE



Dependent Reference of Celerra_CIFSProtocolEndpoint

Celerra_HostedAccessPoint_CIFSS_TCPPE

Table 73. Referenced Properties/Methods for Celerra_HostedAccessPoint_CIFSS_TCPPE



Dependent Reference of Celerra_TCPProtocolEndpoint

Celerra_HostedAccessPoint_CIFSS_IPPE

Table 74. Referenced Properties/Methods for Celerra_HostedAccessPoint_CIFSS_IPPE

84




Dependent Reference of Celerra_IPProtocolEndpoint

Celerra_HostedAccessPoint_NFSS_NFSPE

Table 75. Referenced Properties/Methods for Celerra_HostedAccessPoint_NFSS_NFSPE



Dependent Reference of Celerra_NFSProtocolEndpoint

Celerra_HostedAccessPoint_NFSS_TCPPE

Table 76. Referenced Properties/Methods for Celerra_HostedAccessPoint_NFSS_TCPPE




Celerra_HostedAccessPoint_NFSS_IPPE

Table 77. Referenced Properties/Methods for Celerra_HostedAccessPoint_NFSS_IPPE




Celerra_BindsTo_TCPPE_CIFSPE

Table 78. Referenced Properties/Methods for Celerra_BindsTo_TCPPE_CIFSPE


Antecedent Reference of Celerra_TCPPotocolEndpoint


Celerra_BindsTo_TCPPE_NFSPE

Table 79. Referenced Properties/Methods for Celerra_BindsTo_TCPPE_NFSPE


85


Antecedent Reference of Celerra_TCPPotocolEndpoint


Celerra_BindsTo_IPPE_TCPPE

Table 80. Referenced Properties/Methods for Celerra_BindsTo_IPPE_TCPPE


Antecedent Reference of Celerra_IPPotocolEndpoint


Celerra_DeviceSAPImplementation_DMEP_IPPE

Table 81. Referenced Properties/Methods for Celerra_DeviceSAPImplementation_DMEP_IPPE


Antecedent Reference of Celerra_DMEthernetPort


Celerra_DeviceSAPImplementation_DMEP_CIFSPE

Table 82. Referenced Properties/Methods for Celerra_DeviceSAPImplementation_DMEP_CIFSPE




Celerra_DeviceSAPImplementation_DMEP_NFSPE

Table 83. Referenced Properties/Methods for Celerra_DeviceSAPImplementation_DMEP_NFSPE




Celerra_SystemDevice_DMCS_DMPE

Table 84. Referenced Properties/Methods for Celerra_SystemDevice_DMCS_DMEP


GroupComponent Reference of Celerra_DataMoverComputerSystem

86


PartComponent Reference of Celerra_DMEthernetPort

Celerra_SystemDevice_VDMCS_DMPE

Table 85. Referenced Properties/Methods for Celerra_SystemDevice_VDMCS_DMEP


GroupComponent Reference of Celerra_VirtualDataMoverComputerSystem

PartComponent Reference of Celerra_DMEthernetPort

87


File System Manipulation Profile

Overview

The File System Manipulation Profile is a subprofile providing support of configuring and manipulating file systems in the context of file system profiles consisting of the NAS Head and the Self-Contained NAS Profiles. A number of other profiles and subprofiles make use of the elements of the file system profiles.

NOTE: For more details, refer to Clause 10: File System Manipulation Profile in Storage Management Technical Specification, Part 4 FileSystems Version 1.6.0, Revision 4.

Class Diagram

Figure 14. File System Manipulation Class Diagram


Supported Extrinsic Methods

Implemented in Celerra_FileSystemConfigurationCapablities.SupportedSynchronousMethods and Celerra_FileSystemConfigurationCapablities.SupportedAsynchronousMethods.

Extrinsic methods in File System Manipulation Profile are all synchronous methods including SNIA_CreateFileSystem, DeleteFileSystem, SNIA_ModifyFileSystem and CreateGoalSettings.

88


Celerra_UxfsFileSystemCapabilities.CreateGoalSettings

NOTE: The output of Celerra_UxfsFileSystemCapabilities.CreateGoalSettings will be ignored as input parameter ‘Goal’ in SNIA_CreateFileSystem and SNIA_ModifyFileSystem.

Celerra_LocallyAccessibleFileSystemCapabilities.CreateGoalSettings

This method will return a Celerra_LocallyAccessibleFileSystemSetting element that may be used for enabling a FileSystem to locally access to a File Server by the methods SNIA_CreateFileSystem and SNIA_ModifyFileSystem.

NOTE: Only the property ‘ReadWritePolicy’ is supported in CreateGoalSettings. Supported value list for 'ReadWritePolicy’ is {3: Read/Write}.

File System Manipulation

NOTE: For further information, refer to:

File System Creation

File System Modification

File System Deletion

File System Creation

The following factors shall be considered when creating a FileSystem via SMI-S Provider by invoking Celerra_FileSystemConfigurationService.SNIA_CreateFileSystem:

FileSystem Name Pattern

1. A file system name CAN include upper and lowercase letters, numbers, hyphens (-), underscores (_), and periods (.).

2. A file system name can NOT begin with a hyphen, period, or the word root or include a blank character or a colon (:).

3. A file system name can NOT be a single integer or be comprised entirely of integers. Alphanumeric names are accepted.

4. A file system name is limited to 240 bytes (represented as 240 ASCII characters or a variable number of Unicode multi-byte characters).

FileSystem Mountpoint Pattern

1. The pathname must begin with a forward slash (/).

2. The pathname is limited to 255 bytes (represented as 255 ASCII characters or a variable number of Unicode multi-byte characters).

3. The pathname can include upper and lowercase letters, numbers, forward slashes, hyphens (-), underscores (_), and periods (.).

Local Access Required

1. Local access information including FileServer and LocalAccessSetting is mandatory in FileSystem creation. But LocalAccessPoint is optional.

2. ReadWritePolicy in Access Setting MUST be set to {3: Read/Write}.

3. The newly created FileSystem will be automatically mounted to the Data Mover that hosts the File Server provided by client. The ‘mount point’ will be set to the same as LocalAccessPoint if provided; otherwise, the name of the FileSystem will be used as a default mount point as “/<FileSystemName>”.

4. The other File Servers hosted by the same Data Mover will share the local access with the File Server used by FileSystem creation.

89


FileSystem is ONLY supported to be created from StoragePool rather than StorageExtent.

FileSytem is ONLY supported to be created with capacity which is equal or greater than 2MB.

Signature and Parameters of Celerra_FileSystemConfigurationService.SNIA_CreateFileSystem are described as follows:

Table 86. Signature and Parameters of SNIA_CreateFileSystem

Parameter Qualifiers Description

ElementName IN, Required The name of the FileSystem to be created. It should follow the FileSystem Naming Pattern defined in File System Creation.

Job OUT, Not supported This method is synchronous.

Goal IN, Ignored

TheElement OUT Reference to the newly created FileSystem.

InExtents IN, Ignored FileSystem is ONLY supported to be created from StoragePool rather than StorageExtent.

Pools IN, Required

Reference to the StoragePools from which LogicalDisk will be created automatically and on which the FileSystem being created will reside. In VNX File, ONLY one StoragePool will be used when creating FileSystem. Therefore, whenever the client provides more than 1 pool in Pools, ONLY the 1st StoragePool will be used and rest of the StoragePools will be ignored.

Sizes IN, OUT, Required

Capacity specified in bytes of the FileSystem to be created. It is in accordance with parameter Pools, and since SMI-S provider will only use 1

st StoragePool,

ONLY 1st value of Sizes will be used.

ExtentSettings IN, Ignored

FileServer IN, Required Reference to the FileServer that will have local access to the FileSystem to be created.

LocalAccessPoint IN, OUT, Optional An opaque string to be used as a path name to access the FileSystem for FileServer.

LocalAccessSetting IN, Required Specifies the settings to enable the FileSystem to be locally accessible from the ComputerSystem indicated by FileServer.

DirectoryServer IN, Ignored

File System Modification

In VNX for File, the following factors shall be considered when modifying a FileSystem via SMI-S Provider by invoking Celerra_FileSystemConfigurationService.SNIA_ModifyFileSystem:

Modification Support

FileSystem Name can be modified.

FileSystem Size can be extended, but the space to expand has to come from the same pool used to create the FileSystem.

90


FileSystem Local Access Setting can NOT be modified including Access Server, Access Point, Read Write Policy and etc.

Signature and Parameters of Celerra_FileSystemConfigurationService.SNIA_ ModifyFileSystem are described as follows:

Table 87. Signature and Parameters of SNIA_ModifyFileSystem


ElementName IN, Optional New name of the FileSystem to be modified. It should follow the FileSystem Naming Pattern defined in File System Creation.


Goal IN, Ignored

TheElement INPUT, Required Reference to the FileSystem to be modified.

InExtents IN, Ignored

Pools IN, Optional

Reference to the Pool on which the FileSystem being modified will be extended. In VNX for File, ONLY one StoragePool will be used when modifying FileSystem. Therefore, whenever the client provides more than 1 pool in Pools, ONLY the 1st StoragePool will be used and the rest of the StoragePools will be ignored.

Sizes IN, OUT, Required if Pools[] provided

Size in bytes to be extended for the FileSystem. It is in accordance with parameter Pools, and since SMI-S provider will only use 1st StoragePool, ONLY 1st value of Sizes will be used.

ExtentSettings IN, Ignored

FileServer IN, Not Supported Modification of Local Access is not supported.

LocalAccessPoint IN, Not Supported Modification of Local Access is not supported.

LocalAccessSetting IN, Not Supported Modification of Local Access is not supported.

InUseOptions IN, Ignored

WaitTime IN, Ignored

File System Deletion

Signature and Parameters of Celerra_FileSystemConfigurationService.DeleteFileSystem are described as follows:

Table 88. Signature and Parameters of DeleteFileSystem



TheElement INPUT, Required Reference to the FileSystem to be deleted.



91


Use Case: Create a locally accessible file system on a storage pool

This use case describes how to create a locally accessible FileSystem from a StoragePool.

Use Case: Create Locally Accessible Filesystem on StoragePool

Create Supported Local Access Settings(This is a negotiation between client and provider)

Get Preconditions(Refer to case in NAS Head profile)

Get NAS Head ComputerSystem

Travers CIM_HostedService to SNIA_FileSystemConfigurationService

Get StoragePool Get File Server

Travers CIM_HostedDependency to SNIA_LocallyAccessibleFileSystemCapabilities

Invoke Method CreateGoalSettings() to get SupportedGoalSettings

Settings satisfied

Modify returned setting and use it as TemplateGoalSettings(input)

N

Goal setting created

Y

Invoke Method SNIA_FileSystemConfigurationService.SNIA_CreateFileSystem()

Input Parameters

Pools LocalAccessSetting

FileServer

Other parametersElementName, Sizes, LocalAccessPoint, …...

Done

Figure 15. Flowchart of Creating Locally Accessible File System on StoragePool

92


Use Case: Increase the size of a file system

This use case describes how to increase the size of afFile system:

Use Case: Increase the size of a Filesystem

Get Filesystem to be extended(Refer to case in File System profile)




Get StoragePool

Invoke Method SNIA_FileSystemConfigurationService.SNIA_ModifyFileSystem()

Input Parameters

PoolsOther parametersSizes (to be extended)

Done

CIM_LocalFileSystem

TheElement

Figure 16. Flowchart of Increasing size of file system

93


Use Case: Modify the name of a file system

This use case shows how to modify the name of a file system:

Use Case: Modify the name of a Filesystem

Get Filesystem to be extended(Refer to case in File System profile)




Invoke Method SNIA_FileSystemConfigurationService.SNIA_ModifyFileSystem()

Input Parameters

Other parametersElementName (new name)

Done

CIM_LocalFileSystem

TheElement

Figure 17. Flowchart of Modifying FileSystem Name

Use Case: Delete a file system and return underlying StorageExtent

Users can invoke SNIA_FileSystemConfigurationService.DeleteFileSystem to delete a FileSystem.

The underlying StorageExtent used by the FileSystem will be recycled automatically. This is transparent to users.

Use Case: Get locally accessible capabilities from a file server ComputerSystem

This use case describes how to get LocallyAccessibleFileSystemCapabilities from a File Server to view Local Access Configuration Capabilities of the File Server.

For further information, refer to Use Case: Create a Locally Accessible Filesystem on a Storage Pool.

Use Case: Get the local access setting for a FileSystem on a File Server ComputerSystem

For further information, refer to Use Case: Get the Local Access Settings for a given FileSystem on the specified File Server.

Use Case: FileSystem Manipulation supported capabilities patterns

The following table lists the pattern that is supported in VNX SMI-S Provider.

Table 89. FileSystem Manipulation Supported Capabilities Patterns

Supported ActualFileSystem

Supported Synchronous

Supported Asynchronous

Initial Availability

94


Types Methods Methods

Any

SNIA_CreateFileSystem, DeleteFileSystem,

SNIA_ModifyFileSystem, CreateGoalSettings

None Any

CIM_Element

The implemented classes and associations related to the File System Manipulation Profile in VNX File Storage System can be described as follows:

Table 90. CIM Elements for File System Manipulation Profile


CIM_ElementCapabilities

Celerra_ElementCapabilities

Celerra_ElementCapabilities_FSCS_FSC

Celerra_ElementCapabilities_FSCS_LAFSC

Celerra_ElementCapabilities_FSCS_FSCC

Associates Capabilities with the FileSystem Configuration Service.


Celerra_HostedDependency

Celerra_HostedDependency_CIFS_LAFSC

Celerra_HostedDependency_NFS_LAFSC

Associates Local Access Configuration Capabilities with the scoping File Server ComputerSystem.

Celerra_HostedDependency

Celerra_HostedDependency_CIFS_LAFSS

Celerra_HostedDependency_NFS_LAFSS

Associates Local Access FileSystem Setting with the scoping File Server ComputerSystem.

CIM_HostedService Celerra_HostedService_CCS_FSCS

Associates FileSystem Configuration Service with the scoping ComputerSystem (NAS Head).

CIM_SettingsDefineCapabilities

Celerra_SettingsDefineCapabilities

Celerra_SettingsDefineCapabilities_FSC_FSS

Celerra_SettingsDefineCapabilities_LAFSC_LAFSS

Associates Settings with Capabilities.

SNIA_FileSystemCapabilities Celerra_UxfsFileSystemCapabilities

Capabilities of the FileSystem Configuration Service for managing FileSystems.

95


SNIA_FileSystemConfigurationCapabilities

Celerra_FileSystemConfigurationCapabilities

Management capabilities of FileSystem Configuration Service.

SNIA_FileSystemConfigurationService

Celerra_FileSystemConfigurationService

Provides the methods to manage FileSystems.

SNIA_LocallyAccessibleFileSystemCapabilities

Celerra_LocallyAccessibleFileSystemCapabilities

Represents the Local Access Configuration Capabilities of the File System Configuration Service.

This class provides a CreateGoalSettings method that will return a SNIA_LocallyAccessibleFileSystemSetting element that may be used for making a FileSystem locally accessible to a file server ComputerSystem by the methods SNIA_CreateFileSystem and SNIA_ModifyFileSystem.

Celerra_FileSystemConfigurationService

Table 91. Referenced Properties/Methods for Celerra_FileSystemConfigurationService





Name The name of the instance.

Caption The short textual description for this object.


SNIA_CreateFileSystem() Creates a LocalFileSystem as specified by parameters and Capabilities of the service and returns a reference to it.

SNIA_ModifyFileSystem () Modifies a LocalFileSystem indicated by a reference and as specified by reference parameters and capabilities of the service.

DeleteFileSystem () Deletes a LocalFileSystem indicated by reference.

Celerra_FileSystemConfigurationCapabilities

Table 92. Referenced Properties/Methods for Celerra_FileSystemConfigurationCapabilities


96


InstanceID A unique identifier of the instance.



BlockStorageCreationSupport Whether the creation and modification of a FileSystem may use already existing LogicalDisk or if a new one must be created if needed.

InitialAvailability Indicates the default state of availability in which the FileSystem Configuration Service can create the FileSystem.

DirectoryServerParameterSupport If the created FileSystem must support security principle.

LocalAccessibilitiySupport If the FileSystem implementation requires a local access specification.

SupportedActualFileSystemType Actual FileSystem type that the FileSystem Configuration Service supports.

SynchronousMethodsSupport An array of methods of the service that supported as synchronous methods.

AsynchronousMethodsSupport An array of methods of the service that supported as asynchronous methods.

Celerra_UxfsFileSystemCapabilities

Table 93. Referenced Properties/Methods for Celerra_UxfsFileSystemCapabilities





SupportedActualFileSystemType Actual FileSystem type that the FileSystem Configuration Service supports.

SupportedProperties An array of property names of the Setting that this Capabilities element supports.

Celerra_LocallyAccessibleFileSystemCapabilities

Table 94. Referenced Properties/Methods for Celerra_LocallyAccessibleFileSystemCapabilities



97





CreateGoalSettings()

This extrinsic method supports the creation of a

LocalAccessibleFileSystemSetting that will be used in SNIA_CreateFileSystem() and SNIA_ModifyFileSystem().

Celerra_HostedService_CCS_FSCS

Table 95. Referenced Properties/Methods for Celerra_HostedService_CCS_FSCS


Antecedent Reference of Celerra_CelerraComputerSystem

Dependent Reference of Celerra_FileSystemConfigurationService

Celerra_HostedDependency_CIFS_LAFSC

Table 96. Referenced Properties/Methods for Celerra_HostedDependency_CIFS_LAFSC



Dependent Reference of Celerra_LocalAccessibleFileSystemCapabilities

Celerra_HostedDependency_NFS_LAFSC

Table 97. Referenced Properties/Methods for Celerra_HostedDependency_NFS_LAFSC



Dependent Reference of Celerra_LocalAccessibleFileSystemCapabilities

Celerra_HostedDependency_CIFS_LAFSS

For further information, refer to Celerra_HostedDependency_CIFSS_LAFSS in File System Profile.

Celerra_HostedDependency_NFS_LAFSS

For further information, refer to Celerra_HostedDependency_NFSS_LAFSS in File System Profile.

Celerra_ElementCapabilities_FSCS_FSC

Table 98. Referenced Properties/Methods for Celerra_ElementCapabilities_FSCS_FSC

98



ManagedElement Reference of Celerra_FileSystemConfigurationService

Capabilities Reference of Celerra_UxfsFileSystemCapabilities

Celerra_ElementCapabilities_FSCS_LAFSC

Table 99. Referenced Properties/Methods for Celerra_ElementCapabilities_FSCS_LAFSC



Capabilities Reference of Celerra_LocallyAccessibleFileSystemCapabilities

Celerra_ElementCapabilities_FSCS_FSCC

Table 100. Referenced Properties/Methods for Celerra_ElementCapabilities_FSCS_FSCC



Capabilities Reference of Celerra_FileSystemConfigurationCapabilities

Celerra_SettingsDefineCapabilities_FSC_FSS

Table 101. Referenced Properties/Methods for Celerra_SettingsDefineCapabilities_FSC_FSS


GroupComponent Reference of Celerra_UxfsFileSystemCapabilities

PartComponent Reference of Celerra_FileSystemSetting

Celerra_SettingsDefineCapabilities_LAFSC_LAFSS

Table 102. Referenced Properties/Methods for Celerra_SettingsDefineCapabilities_LAFSC_LAFSS


GroupComponent Reference of Celerra_LocallyAccessibleFileSystemCapabilities

PartComponent Reference of Celerra_LocallyAccessibleFileSystemSetting

99


File Export Manipulation Profile

Overview

The File Export Manipulation Profile is a subprofile of autonomous profiles that support FileSystems. It utilizes the elements of the File System subprofiles and supports creation, modification and deletion of FileShares that are exported by the File Export Subprofile. A number of the other profiles and subprofiles also make use of elements of the File System subprofile. In this specification, these profiles and subprofiles will be referred to “Filesystem related profiles” -- these include but are not limited to the File System subprofile, the File System Manipulation Subprofile, the File Export Subprofile, the NAS Head Profile, and so on.

Class Diagram

Figure 18. File Export Manipulation Class Diagram


Supported Extrinsic Methods

Implemented in Celerra_FileExportCapablities.SupportedSynchronousMethods and Celerra_FileExportCapablities.SupportedAsynchronousMethods.

Extrinsic methods in File Export Manipulation Profile are all synchronous methods including SNIA_CreateExportedShare, ReleaseExportedShare, SNIA_ModifyExportedShare, AssignePrivilegeToExportedShare, and CreateGoalSettings.

Supported Goal Settings

100


NOTE: For further information, refer to Supported Goal Settings.

Exported Share Manipulation

NOTE: For further information, refer to Exported Share Creation, Exported Share Modification and Exported Share Deletion.

Supported Goal Settings

Implemented in Celerra_ExportedFileShareCapabilities.CreateGoalSettings. The following settings are supported in VNX File.

Table 103. Supported Goal Settings for File Share Creation and Modification

Supported Setting Exported NFS Share Exported CIFS Share

DefaultReadWrite Read/Write (Default)

No Access

Read Only

Read/Write (Default)

CASupported False (Default) True (Default)

False

NOTE: Client must negotiate with SMI-S to get supported goal setting and pass it to SMI-S again when creating/modifying exported share.

Exported Share Creation

In VNX for File, the following factors shall be considered when creating a File Share via SMI-S Provider by invoking Celerra_FileExportService.SNIA_CreateExportedShare:

File Share Name Pattern

1. Share names cannot include the following characters: /, \, %, ", NUL (Null character), STX (start of header), SOT (start of text), and LF (line feed).

2. Share names can contain spaces and other non-alpha-numeric characters but must be enclosed by quotes if spaces are used.

3. Share names cannot begin with a - (hyphen).

4. Share name length is limited to 12 characters unless Unicode support is enabled, in which case the limit is 80 characters.

File Share Path Pattern

1. The export path should be a subfolder for the mountpoint path of the selected FileSystem. So it should follow FileSystem Mountpoint Pattern.

CASupported for CIFS Share

1. If source FileSystem is mounted to Data Mover/VDM with smbca, client can create CIFS share with CA based on the FileSystem via SMI-S.

2. If source FileSystem is not mounted with smbca and un-exported (no CIFS or NFS shares exported from it), client can create CIFS share with CA based on the FileSystem. In this case, SMI-S Provider will firstly unmount the FileSystem and remount the FileSystem with smbca option. Then SMI-S Provider create CIFS share. This is transparent to client.

3. If source FileSystem is not mounted with smbca but exported (there is CIFS or NFS share exported from it), client cannot create CIFS share with CA from the Filesyste and will receive an error from SMI-S provider.

101


Signature and Parameters of Celerra_FileExportService.SNIA_CreateExportedShare are described as follows:

Table 104. Signature and Parameters of SNIA_CreateExportedShare


ElementName IN, Required Name of the share to be created. It should follow the File Share Naming Pattern defined in Exported Share Creation.

Comment IN, Optional User comment for the newly created share.


Root IN, Required Reference to the source FileSystem where the newly created File Share based on.

SharedElementPath IN, Optional

A path to the shared element, either file or directory, from the root directory of the FileSystem indicated by Root.

If not provided, mountpoint of the FileSystem will be used as a default share path.

Goal IN, Required Embedded instance for ExportedFileShare Setting contains configuration settings of the newly created share specified by client.

TheShare OUT Reference to the newly created File Share.

DefaultUserId IN, Ignored

RootAccessHosts IN, Optional An array that specifies the hosts that have root access to this File Share. It only takes effect on NFS Share as VNX for File uses ACL for CIFS Share access control.

AccessPoints IN, Ignored

Exported Share Modification

In VNX for File, the following factors shall be considered when modifying a File Share via SMI-S Provider by invoking Celerra_FileExportService.SNIA_ModifyExportedShare:

Modification Support

Share Name can NOT be changed.

Share Path can NOT be changed.

Share DefaultUserId can NOT be changed.

Share AccessPoints can NOT be changed.

Modify RootAccessHosts is ONLY supported for NFS Share.

Modify CASupported (in Goal) is ONLY support for CIFS Share.

Modify DefaultReadWrite (in Goal) is ONLY supported for CIFS Share.

Signature and Parameters of Celerra_FileExportService.SNIA_ModifyExportedShare are described as follows:

Table 105. Signature and Parameters of SNIA_ModifyExportedShare


102


ElementName IN, Not supported Modify share name is not supported.

Comment IN, Optional User comment for the share to be modified.


Root IN, Required Reference to the source FileSystem where the File Share based on.

SharedElementPath IN, Not supported Modify share path is not supported.

Goal IN, Required Embedded instance for ExportedFileShare Setting contains configuration settings of the share to be modified.

TheShare IN, Required Reference to the File Share to be modified.

DefaultUserId IN, Not supported

RootAccessHosts IN, Optional An array that specifies the hosts that have root access to this File Share. It only takes effect on NFS Share as VNX for File uses ACL for CIFS Share access control.

AccessPoints IN, Not supported

InUseOptions IN, Not supported

WaitTime IN, Not supported

Exported Share Deletion

Signature and Parameters of Celerra_FileExportnService.ReleaseExportedShare are described as follows:

Table 106. Signature and Parameters of ReleaseExportedShare



TheShare INPUT, Required Reference to the File Share to be deleted.



Privilege Assignment

For further information, refer to Privilege Manipulation.

Use Case: File Export Manipulation supported capabilities patterns

The following table lists the supported capabilities pattern of File Export Manipulation in VNX SMI-S Provider:

Table 107. File Export Manipulation Supported Capabilities Patterns

FileSharingProtocols SynchronousMethods AsynchronousMethods InitialExportState

CIFS, NFS Export Creation

Export Modification Export Deletion

None Any

103


Use Case: Create a FileShare for export

This use case describes how to create an exported share.

Use Case: Create a File Share for ExportPreconditions: The File Server (that hosts the share) and Filesystem (from which the share will be exported) were defined previously.

Create Supported Exported Share Settings(This is a negotiation between client and provider)

Get Scoping File Server(Refer to case in NAS Head profile)

Get File Server

Travers CIM_HostedService to SNIA_FileExportService

Travers ElementCapabilities to SNIA_ExportedFileShareCapabilities


Settings satisfied


N


Y

Invoke Method SNIA_FileExportService.SNIA_CreateExportedShare()

Input Parameters

Goal

Other parametersElementName, SharedElementPath, …...

Done

Get Root Filesystem(Refer to case in Filesystem profile)

Get Filesystem

Root

Figure 19. Flowchart of Creating Exported File Share

104


Use Case: Modification of an exported FileShare

This use case describes how to modify an exported share.

Use Case: Modify Exported File SharePreconditions: The File Share to be modified was defined previously.

Create Supported Exported Share Settings(This is a negotiation between client and provider)

Travers CIM_ServiceAffectsElements to SNIA_FileExportService

Travers ElementCapabilities to SNIA_ExportedFileShareCapabilities


Settings satisfied


N


Y

Invoke Method SNIA_FileExportService.SNIA_ModifyExportedShare()

Input Parameters

Goal

Other parametersRootAccessHosts, …...

Done

Root

Travers CIM_SharedElement to CIM_LocalFileSystem

TheShare

TheShare(File Share to be modified)

Figure 20. Flowchart of Modifying Exported File Share

105


Use Case: Removal of an exported FileShare

This use case describes how to release exported share.

Use Case: Release Exported File SharePreconditions: The File Share to be released was defined previously.

Travers CIM_ServiceAffectsElements to SNIA_FileExportService

Invoke Method SNIA_FileExportService.ReleaseExportedShare()

Input Parameters

Done

TheShare

TheShare(File Share to be modified)

Figure 21. Flowchart of Releasing Exported File Share

CIM Element

The implemented classes and associations related to the File Export Manipulation Profile in VNX File Storage System can be described as follows:

Table 108. CIM Elements for File Export manipulation Profile


CIM_ElementCapabilities Celerra_ElementCapabilities_FES_FEC

Associates the File Export Capabilities element with the File Export Service.

CIM_ElementCapabilities Celerra_ElementCapabilities_FES_EFSC

Associates the Exported File Share Capabilities element with the File Export Service.

CIM_HostedService

Celerra_HostedService (File Export)

Celerra_HostedService_NFSS_FES

Celerra_HostedService_CIFSS_FES

Associates the File Export Service with it scoping system (File Server, NFS or CIFS).

CIM_ServiceAffectsElement Celerra_ServiceAffectsEleme Associates the Export File Share with

106


nt

Celerra_ServiceAffectsElement_FES_NFSS

Celerra_ServiceAffectsElement_FES_CIFSS

the File Export Service.

CIM_SettingsDefineCapabilities

Celerra_SettingsDefineCapabilities_EFSC_EFSS

Associates the Export File Share Capabilities with the Export File Share Settings.

SNIA_ExportedFileShareCapabilities

Celerra_ExportedFileShareCapabilities

Represents the Capabilities of the File Export Service for managing FileShares of a specific file sharing protocol (and version).

SNIA_ExportedFileShareSetting (File Share)

Celerra_ExportedFileShareSetting (File Share)

Configuration settings for an exported File Share.

SNIA_ExportedFileShareSetting (pre-define)

Celerra_ExportedFileShareSetting (pre-define)

Pre-defined configuration settings for exported FileShares that is used to define a Capabilities element associated with the FileExportService.

SNIA_FileExportCapabilities Celerra_FileExportCapabilities

Represents the management capabilities of the File Export Service.

SNIA_FileExportService Celerra_FileExportService Provides methods for managing exported File Share.

Celerra_FileExportService

Table 109. Referenced Properties/Methods for Celerra_FileExportService





Name The name of the instance.



SNIA_CreateExportedShare() Creates a FileShare element configured for exporting a file or directory as a share.

SNIA_ModifyExportedShare() Modifies the configuration of a FileShare element setup to export a file or directory as a share.

107


ReleaseExportedShare() Deletes the FileShare element that is exporting a file or directory as a share and releases that element.

AssignePrivilegeToExportedShare() Assigns privilege to an Identity on the FileShare element to control the access activities.

Celerra_FileExportCapabilities

Table 110. Referenced Properties/Methods for Celerra_FileExportCapabilities





CASupported Whether Continuous Availability (CA) supported by the File Server.

InitialEnableState Indicates the enabled/disabled states to which the File Export Service can initialize the created FileShare.

FileSharingProtocol The file sharing protocol that the File Export Service supports

SynchronousMethodsSupport An array of methods of the service that are supported as synchronous methods.

AsynchronousMethodsSupport An array of methods of the service that are supported as asynchronous methods.

Celerra_ExportedFileShareCapabilities

Table 111. Referenced Properties/Methods for Celerra_ExportedFileShareCapabilities





CASupported Whether Continuous Availability (CA) supported by the File Server.

FileSharingProtocol The file sharing protocol that the File Export Service supports


108


CreateGoalSettings()

This extrinsic method supports the creation of an ExportedFileShareSetting that will be used in SNIA_CreateExportedShare() and SNIA_ModifyExportedShare().

Celerra_ExportedFileShareSetting

For further information, refer to Celerra_ExportedFileShareSetting in File Export Profile.

Celerra_HostedService_NFSS_FES

Table 112. Referenced Properties/Methods for Celerra_HostedService_NFSS_FES



Dependent Reference of Celerra_FileExportService

Celerra_HostedService_CIFSS_FES

Table 113. Referenced Properties/Methods for Celerra_HostedService_CIFSS_FES



Dependent Reference of Celerra_FileExportService

Celerra_ElementCapabilities_FES_FEC

Table 114. Referenced Properties/Methods for Celerra_ElementCapabilities_FES_FEC


ManagedElement Reference of Celerra_FileExportService

Capabilities Reference of Celerra_FileExportCapabilities

Celerra_ElementCapabilities_FES_EFSC

Table 115. Referenced Properties/Methods for Celerra_ElementCapabilities_FES_EFSC


ManagedElement Reference of Celerra_FileExportService

Capabilities Reference of Celerra_ExportedFileShareCapabilities

Celerra_SettingsDefineCapabilities_EFSC_EFSS

Table 116. Referenced Properties/Methods for Celerra_SettingsDefineCapabilities_EFSC_EFSS

109



GroupComponent Reference of Celerra_ExportedFileShareCapabilities

PartComponent Reference of Celerra_ExportedFileShareSetting

Celerra_ServiceAffectsElement_FES_NFSS

Table 117. Referenced Properties/Methods for Celerra_ServiceAffectsElement_FES_NFSS


AffectedElement Reference of Celerra_NFSShare

AffectingElement Reference of Celerra_FileExportService

Celerra_ServiceAffectsElement_FES_CIFSS

Table 118. Referenced Properties/Methods for Celerra_ServiceAffectsElement_FES_CIFSS


AffectedElement Reference of Celerra_Identity

AffectingElement Reference of Celerra_FileExportService

110


Multiple Computer System profile

Overview

The Multiple Computer System Subprofile allows a client to retrieve information about the redundancy configuration and the capabilities of the NAS system. This subprofile models multiple systems that cooperate to present a “virtual” computer system with additional capabilities or redundancy.

NOTE: For more details, refer to Clause 30: Multiple Computer System Subprofile in Storage Management Technical Specification, Part 2 Common Profiles, Version 1.5.0, Revision 6.

Class Diagram

Figure 22. Multiple Computer System Class Diagram


Type of RedundancySet

Implemented in RedundancySet.TypeOfSet. In VNX for File, the value of ‘TypeOfSet’ is set to {5: Limited Sparing}. This means all members are active, and they may or may not be aware of each other and they are not spares for each other. Instead, their redundancy is indicated by the IsSpare relationship.

Redundancy Status

Implemented in RedundancySet.RedundancyStatus.

111


If none of Data Movers is configured as standby, SMI-S will report Celerra_CelerraRedundancySet.RedundancyStatus with value {4: Redundancy Lost}. If one or more Data Mover(s) is/are configured as standby, value {2: Fully Redundant} will be reported.

Use Case: Find Top-level Computer Systems

In VNX File Storage System, the Top-level ComputerSystem is the NAS Head ComputerSystem. For further information, refer to Use Case: Discover NAS Head.

Use Case: Find the Top-level Computer System for LogicalDevice

From LogicalDevice (including LogicalDisk, PrimordialStorageExtent, EthernetPort), traverse CIM_SystemDevice to CIM_ComputerSystem to get the scoping system.

Taking the scoping system as PartComponent, traverse CIM_ComponentCS to CIM_ComputerSystem(GroupComponent). If no result, the scoping system is already the Top-level; otherwise the result is the Top-level since all component systems must be associated with Top-level system via CIM_CompomentCS.

Use Case: Find the Top-level Computer System for LogicalDevicePrecondition: LogicalDevice was obtained previosly.

Check if Scoping System is Top-levelGet Scoping System

Travers CIM_SystemDevice to CIM_ComputerSystem

Travers CIM_ComponentCS to CIM_ComputerSystem(GroupComponent)

Got Instance

Scoping system is Top-levelResult system is Top-level

Y N

Done

CIM_LogicalDevice

Figure 23. Flowchart of Finding Top-level Computer System for LogicalDevice

CIM Element

The implemented classes and associations related to the Multiple Computer System Profile in VNX File Storage System can be described as follows:

Table 119. CIM Elements for Multiple Computer System Profile


CIM_ComponentCS Celerra_ComponentCS Associates Non-top-level system with

112




Celerra_ComponentCS_CCS_PDMCS

Celerra_ComponentCS_CCS_PCSCS

the Top-level system.

CIM_ComputerSystem


Top-level CS and NAS Head of VNX File.


Primary and Standby Data Mover in VNX File.

Celerra_VirtualDataComputerSystem

Virtual Data Mover (VDM) in VNX File.

Celerra_PhysicalDataMoverComputerSystem

Physical host where data service is running on.

Celerra_PhysicalControlStationComputerSystem

Physical host where storage management service running on.

CIM_ConcreteIdentity

Celerra_ConcreteIdentity (RedundancySet)

Celerra_ConcreteIdentity_CCS_CRS

Celerra_ConcreteIdentity_DMCS_DMRS

Celerra_ConcreteIdentity_VDMCS_VDMRS

Associates ComputerSystem with RedundancySet


Celerra_HostedDependency (Virtual File Server)




Associates virtual File Server with the ComputerSystem that hosts the File Server.

CIM_IsSpare Celerra_IsSpare_DMCS_CRS

Associates standby Data Mover with the RedundancySet that aggregates the Data Movers.

CIM_MemberOfCollection

Celerra_MemberOfCollection

Celerra_MemberOfCollection_CRS_DMCS

Associates RedundancySet with its member ComputerSystems.

113


Celerra_MemberOfCollection_CRS_VDMCS

Celerra_MemberOfCollection_DMRS_PDMCS

Celerra_MemberOfCollection_VDMRS_PDMCS

CIM_RedundancySet

Celerra_CelerraRedundancySet

RedundancySet for aggregating Data Movers and Virtual Data Movers.

Celerra_DataMoverRedundancySet

RedundancySet for aggregating Physical Data Movers where data service provided by Data Mover is running.

Celerra_VirtualDataMoverRedundancySet

RedundancySet for aggregating Physical Data Movers where data service provided by Virtual Data Mover is running.


For further information, refer to Celerra_CelerraComputerSystem in NAS Head Profile.


For further information, refer to Celerra_DataMoverComputerSystem in NAS Head Profile.

Celerra_VirtualDataComputerSystem

For further information, refer to Celerra_VirtualDataMoverComputerSystem in NAS Head Profile.

Celerra_PhysicalDataMoverComputerSystem

Table 120. Referenced Properties/Methods for Celerra_PhysicalDataMoverComputerSystem



Name Unique identifier for the Physical Data Mover in a format specified by NameFormat.






114



OperationalStatus Overall status of the Physical Data Mover.

OtherIdentifyingInfo An array of known identifiers for the Data Mover.

PrimaryOwnerContact Contact information of the primary owner of this ComputerSystem.

PrimaryOwnerName The name of the primary owner of this ComputerSystem.

Celerra_PhysicalControlStationComputerSystem

Table 121. Referenced Properties/Methods for Celerra_PhysicalControlStationComputerSystem



Name Unique identifier for the Control Station in a format specified by NameFormat.






OperationalStatus Overall status of the Control Station.

OtherIdentifyingInfo An array of known identifiers for the Control Station.

PrimaryOwnerContact Contact information of the primary owner of this ComputerSystem.

PrimaryOwnerName The name of the primary owner of this ComputerSystem.

Celerra_CelerraRedundancySet

Table 122. Referenced Properties/Methods for Celerra_CelerraRedundancySet


InstanceID A unique identifier for this instance.



115


RedundancyStatus Information of the state of the RedundancyGroup.

TypeOfSet Information of the type of redundancy.

Celerra_DataMoverRedancySet

Table 123. Referenced Properties/Methods for Celerra_DataMoverRedundancySet







Celerra_VirtualDataMoverRedundancySet

Table 124. Referenced Properties/Methods for Celerra_VituralDataMoverRedundancySet








Table 125. Referenced Properties/Methods for Celerra_ComponentCS_CCS_DMCS



PartComponent Reference of Celerra_DataMoverComputerSystem


Table 126. Referenced Properties/Methods for Celerra_ComponentCS_CCS_VDMCS


116



PartComponent Reference of Celerra_VirtualDataMoverComputerSystem

Celerra_ComponentCS_CCS_PDMCS

Table 127. Referenced Properties/Methods for Celerra_ComponentCS_CCS_PDMCS



PartComponent Reference of Celerra_PhysicalDataMoverComputerSystem

Celerra_ComponentCS_CCS_PCSCS

Table 128. Referenced Properties/Methods for Celerra_ComponentCS_CCS_PCSCS



PartComponent Reference of Celerra_PhysicalControstationComputerSystem

Celerra_ConcreteIdentity_CCS_CRS

Table 129. Referenced Properties/Methods for Celerra_ConcreteIdentity_CCS_CRS


SameElement Reference of Celerra_CelerraRedundancySet

SystemElement Reference of Celerra_CelerraComputerSystem

Celerra_ConcreteIdentity_DMCS_DMRS

Table 130. Referenced Properties/Methods for Celerra_ConcreteIdentity_DMCS_DMRS


SameElement Reference of Celerra_DataMoverRedundancySet

SystemElement Reference of Celerra_DataMoverComputerSystem

Celerra_ConcreteIdentity_VDMCS_VDMRS

Table 131. Referenced Properties/Methods for Celerra_ConcreteIdentity_VDMCS_VDMRS


SameElement Reference of Celerra_VirtualDataMoverRedundancySet

117


SystemElement Reference of Celerra_VirtualDataMoverComputerSystem

Celerra_MemberOfCollection_CRS_DMCS

Table 132. Referenced Properties/Methods for Celerra_MemberOfCollection_CRS_DMCS


Collection Reference of Celerra_CelerraRedundancySet

Member Reference of Celerra_DataMoverComputerSystem

Celerra_MemberOfCollection_CRS_VDMCS

Table 133. Referenced Properties/Methods for Celerra_MemberOfCollection_CRS_VDMCS


Collection Reference of Celerra_CelerraRedundancySet

Member Reference of Celerra_VirtualDataMoverComputerSystem

Celerra_MemberOfCollection_DMRS_PDMCS

Table 134. Referenced Properties/Methods for Celerra_MemberOfCollection_DMRS_PDMCS


Collection Reference of Celerra_DataMoverRedundancySet

Member Reference of Celerra_PhysicalDataMoverComputerSystem

Celerra_MemberOfCollection_VDMRS_PDMCS

Table 135. Referenced Properties/Methods for Celerra_MemberOfCollection_VDMRS_PDMCS


Collection Reference of Celerra_VirtualDataMoverRedundancySet

Member Reference of Celerra_PhysicalDataMoverComputerSystem

Celerra_IsSpare_DMCS_CRS

Table 136. Referenced Properties/Methods for Celerra_IsSpare_DMCS_CRS


Antecedent Reference of Celerra_CelerraRedundancySet

Dependent Reference of Celerra_DataMoverComputerSystem

118



For further information, refer to Celerra_HostedDependency_DMCS_CIFSS in NAS Head Profile.


For further information, refer to Celerra_VirtualDataMoverComputerSystem in NAS Head Profile.


For further information, refer to Celerra_HostedDependency_VDMCS_CIFSS in NAS Head Profile.

119


Extent Composition Profile

Overview

The Extent Composition Subprofile allows an implementation that supports the Block Services package to optionally provide an abstraction of how it virtualizes exposable block storage elements from the underlying Primordial storage pool. The abstraction is presented to the client as a representative hierarchy of extents. These extents are instances of CompositeExtents and StorageExtents linked by a combination of CompositeExtentBasedOn and BasedOn associations. The foundation of the hierarchy is a set of Primordial extents.

This subprofile is used optionally with the Array, Virtualization, Self-Contained NAS, NAS Head, and Volume Management profiles. A Primordial storage extent can represent a Disk Drive in the Array or Self-contained NAS, a downstream virtualized Volume used by the Virtualizer or NAS Head Profiles, or an OS Logical Disk in the Volume Management Profile. An exposable block storage element used in this subprofile is defined as a Storage Volume or a Logical Disk.

In the presented hierarchy each dependent extent is formed by those that precede the antecedents in a process of either decomposition or composition.

Decomposition

Decomposition is used to allocate space from an antecedent extent, in order to form a new dependent extent. This allocation may be partial or complete consumption. Complete consumption is the degenerate case in which all space in the antecedent extent is used. In this case the decomposed dependent extent may be either modeled even though it is one to one with the antecedent extent or omitted and the antecedent extent used in its stead.

Composition

Composition is used to form an a dependent extent from antecedent extents in the purpose of either concatenating the antecedent blocks to achieve a size goal, or achieving a Quality Of Service goal such as mirroring the antecedent extents for redundancy, striping the antecedent extents for performance, or striping the antecedent extents with the addition of parity to achieve redundancy.

These extent “productions” can be assembled in a multi-layer hierarchy.

NOTE: For more details, refer to Clause 14: Extent Composition Subprofile in Storage Management Technical Specification, Part 3 Block Devices, Version 1.6.0, Revision 4.

120


Class Diagram

Figure 24. Extent Composition Class Diagram


CompositeExtent and LogicalDisk

In VNX for File, CompositeExtent and LogicalDisk are modeling the same NAS object and the Meta Volume where the FileSystem can reside on.

Use Case: Traverse the virtualization hierarchy of a LogicalDisk

For more information, refer to Use Case: Find the Primordial Extents used by a Logical Disk.

Use Case: Get the Primordial Extents for a SubjectExtent

To get the Primordial Extent, client needs to traverse CIM_BasedOn from subject StorageExtent(Dependent) to upper-level StorageExtent(Antecedent) recursively until the upper level StorageExtent.Primordial is true.

For more information, refer to Use Case: Find the Primordial Extents used by a Logical Disk.

Use Case: Find the Primordial Extents used by a Logical Disk

This use case describes how to get Primordial Extents used by a LogicalDisk.

121


Use Case: Find Primordial Extents Used by a LogicalDiskPre-Condition: LogicalDisk was obtained previously.

Get Primordial Extents for a Subject Extent

Get LogicalDisk

Get LogicalDisk(refer to case NAS Head Profile)

Take CIM_LogicalDisk as the subject extent

Input CIM_StorageExtent

Done

Travers CIM_BasedOn or CIM_CompositeExtentBasedOn to CIM_StorageExtent(Antecedent)

Check CIM_StorageExtent.Primordial

Is True

Input CIM_StorageExtent is PrimordialReturn it

N

Y

Recursively Invoke process“Get Primordial Extents for a Subject Extent”

on CIM_StorageExtent(Antecedent)

Figure 25. Flowchart of Finding Primordial Extents Used by a LogicalDisk

CIM Element

The implemented classes and associations related to the Extent Composition Profile in VNX File Storage System can be described as follows:

Table 137. CIM Elements for Extent Composition Profile


CIM_AssociatedComponentE Celerra_AssociatedCompone Associates StorageExtent with the

122


xtent ntExtent StoragePool.

CIM_AssociatedRemainingExtent

Celerra_AssociatedRemainingExtent

Associates RemaningStorageExtent with the StoragePool.

CIM_BasedOn

Celerra_BasedOn (Top-level)

Celerra_BasedOn_CE_LD

Associates LogicalDisk with the underlying Storage Extent (Composite Extent) it is based on.

Celerra_BasedOn (Mid-level)

Celerra_BasedOn_CNPSE_DNPSE

Celerra_BasedOn_DNPSE_DNPSE

Celerra_BasedOn_PSE_DNPSE

Celerra_BasedOn_CNPSE_RSE

Celerra_BasedOn_DNPSE_RSE

Celerra_BasedOn_PSE_RSE

Associates a Storage Extent (Pool Component or Intermediate) with the underlying Storage Extents it is based on.

Celerra_CompositeExtentBasedOn

Celerra_CompositeExtentBasedOn_CNPSE_CE

Celerra_CompositeExtentBasedOn_DNPSE_CE

Celerra_CompositeExtentBasedOn_CNPSE_CNPSE

Celerra_CompositeExtentBasedOn_DNPSE_CNPSE

Celerra_CompositeExtentBasedOn_PSE_CNPSE

Associates a Composite Extent with the underlying Storage Extents that it virtualizes.

CIM_CompositeExtent Celerra_CompositeExtent

NAS Meta Volume on which FileSystem already resides.

The ExtentDiscriminator property is set to [“SNIA:Intermediate”, “SNIA:Composite”]

CIM_StorageExtent


NAS Disk Volume imported from VNX Block to File.

ExtentDiscriminator property is set to [“SNIA:Imported”]

Celerra_CompositeNonPrimordialStorageExtent

NAS Stripe volume or Meta volume without FileSystem.

123


The ExtentDiscriminator property is set to one or more values of array [“SNIA:Composite”, “SNIA:Intermediate”, “SNIA:Pool Component”]

Celerra_DecompositeNonPrimordialStorageExtent

NAS Slice volume.

The ExtentDiscriminator property is set to one or more values of array [“SNIA:Intermediate”, “SNIA:Pool Component”]

Celerra_RemainingStorageExtent

Free parts of NonPrimordialStorageExtent and PrimordialStorageExtent.

The ExtentDiscriminator property is set to [“SNIA:Remaining”]

Celerra_CompositeExtent

Table 138. Referenced Properties/Methods for Celerra_CompositeExtent


SystemCreationClassName The class Name of scoping system (Top-level Computer System).



DeviceID ID of the volume.

Name The name of the meta volume.

NameFormat The format of the Name.

ExtentStatus Extent status.

ExtentType Type of the composite extent.

ExtentStripeLength Stripe length of the extent.

IsConcatenated Whether the data is concatenated across the various StorageExtent in the group.

OperationalStatus A subset of operational status that is applicable for the StorageExtent.


NumberOfBlocks The number of blocks of this element.

124



ConsumableBlocks The number of blocks usable to consumers.

IsBasedOnUnderlyingRedundancy Indicates whether or not underlying StorageExtent(s) participate in a StorageRedundancyGroup.

NoSinglePointOfFailure Indicates whether or not there is no single point of failure.

DataRedundancy The number of complete copies of data currently maintained.

PackageRedundancy The acceptable number of physical packages in real-time failure without data loss.

DeltaReservation The percentage that specifies the amount of space that should be reserved in a replica for caching changes.




For further information, refer to Celerra_PrimordialStorageExtent in NAS Head Profile

Celerra_CompositeNonPrimordialStorageExtent

Table 139. Referenced Properties/Methods for Celerra_CompositeNonPromordialStorageExtent


SystemCreationClassName Class Name of scoping system (Top-level Computer System).

SystemName Name of the scoping system.

CreationClassName Name of class used to create this instance.

DeviceID Id of the volume.





ConsumableBlocks The number of blocks usable by consumers.


125



Name Name of the disk volume.




Celerra_DecompositeNonPrimordialStorageExtent

Table 140. Referenced Properties/Methods for Celerra_DecompositeNonPromordialStorageExtent










ConsumableBlocks The number of blocks usable by consumers.






Celerra_RemainingStorageExtent

Table 141. Referenced Properties/Methods for Celerra_RemainingStorageExtent


126











ConsumableBlocks The number of blocks usable to consumers.






Celerra_BasedOn_CE_LD

Table 142. Referenced Properties/Methods for Celerra_BasedOn_CE_LD


Antecedent Reference of Celerra_CompositeExtent

Dependent Reference of Celerra_LogicalDisk

Celerra_BasedOn_CNPSE_DNPSE

Table 143. Referenced Properties/Methods for Celerra_BasedOn_CNPSE_DNPSE


Antecedent Reference of Celerra_CompositeNonPrimordialStorageExtent

Dependent Reference of Celerra_DecompositeNonPrimordialStorageExtent

127


Celerra_BasedOn_DNPSE_DNPSE

Table 144. Referenced Properties/Methods for Celerra_BasedOn_DNPSE_DNPSE


Antecedent Reference of Celerra_DecompositeNonPrimordialStorageExtent


Celerra_BasedOn_PSE_DNPSE

Table 145. Referenced Properties/Methods for Celerra_BasedOn_PSE_DNPSE


Antecedent Reference of Celerra_PrimordialStorageExtent


Celerra_BasedOn_CNPSE_RSE

Table 146. Referenced Properties/Methods for Celerra_BasedOn_CNPSE_RSE



Dependent Reference of Celerra_RemainingStorageExtent

Celerra_BasedOn_DNPSE_RSE

Table 147. Referenced Properties/Methods for Celerra_BasedOn_DNPSE_RSE




Celerra_BasedOn_PSE_RSE

Table 148. Referenced Properties/Methods for Celerra_BasedOn_PSE_RSE




Celerra_CompositeExtentBasedOn_CNPSE_CE

Table 149. Referenced Properties/Methods for Celerra_CompositeExtentBasedOn_CNPSE_CE

128




Dependent Reference of Celerra_CompositeExtent

Celerra_CompositeExtentBasedOn_DNPSE_CE

Table 150. Referenced Properties/Methods for Celerra_CompositeExtentBasedOn_DNPSE_CE



Dependent Reference of Celerra_CompositeExtent

Celerra_CompositeExtentBasedOn_CNPSE_CNPSEE

Table 151. Referenced Properties/Methods for Celerra_CompositeExtentBasedOn_CNPSE_CNPSE



Dependent Reference of Celerra_CompositeNonPrimordialStorageExtent

Celerra_CompositeExtentBasedOn_DNPSE_CNPSE

Table 152. Referenced Properties/Methods for Celerra_CompositeExtentBasedOn_DNPSE_CNPSE




Celerra_CompositeExtentBasedOn_PSE_CNPSE

Table 153. Referenced Properties/Methods for Celerra_CompositeExtentBasedOn_PSE_CNPSE




129


Software Profile

Overview

The Software Profile models software or firmware installed in a computer system. Information of the installed software is given using the SoftwareIdentity class. This is linked to the system using an InstalledSoftwareIdentity association.

Firmware is modeled as SoftwareIdentity. InstalledSoftwareIdentity is used for firmware associated with a System.

NOTE: For more details, refer to Clause 38: Software Subprofile in Storage Management Technical Specification, Part 2 Common Profiles, Version 1.5.0, Revision 6.

Class Diagram

Figure 26. Software Class Diagram


Software/Firmware Manufacture

Implemented in Celerra_SoftwareIdentity.Manufacture.

Software/Firmware Version

Implemented in Celerra_SoftwareIdentity.VersionString.

130


From corresponding classes, client can retrieve the software and firmware versions for VNX File, Control Station and Physical Data Mover.

CIM Element

The implemented classes and associations related to the Software Profile in VNX File Storage System can be described as follows:

Table 154. CIM Elements for Software Profile


CIM_InstalledSoftwareIdentity

Celerra_InstalledSoftwareIdentity

Celerra_InstalledSoftwareIdentity_CCS_CSI

Celerra_InstalledSoftwareIdentity_PDMCS_DMSI

Celerra_InstalledSoftwareIdentity_PCSCS_CSSI

Associates the SoftwareIdentity with the corresponding ComputerSystem.

CIM_SoftwareIdentity

Celerra_CelerraSoftwareIdentity

Software information about VNX File Storage System.

Celerra_ControlStationSoftwareIdentity

Software information about Control Station.

Celerra_DataMoverSoftwareIdentity

Firmware information about Physical Data Mover.

Celerra_CelerraSoftwareIdentity

Table 155. Referenced Properties/Methods for Celerra_CelerraSoftwareIdentity


InstanceID Unique identifier for this instance.

VersionString Version of software/firmware.

Manufacturer The information of Manufacturer.


Celerra_ControlStationSoftwareIdentity

Table 156. Referenced Properties/Methods for Celerra_ControlStationSoftwareIdentity


131






Celerra_DataMoverSoftwareIdentity

Table 157. Referenced Properties/Methods for Celerra_DataMoverSoftwareIdentity






Celerra_InstalledSoftwareIdentity_CCS_CSI

Table 158. Referenced Properties/Methods for Celerra_InstalledSoftwareIdentity_CCS_CSI


System Reference of Celerra_CelerraComputerSystem

InstalledSoftware Reference of Celerra_CelerraSoftwareIdentity

Celerra_InstalledSoftwareIdentity_PDMCS_DMSI

Table 159. Referenced Properties/Methods for Celerra_InstalledSoftwareIdentity_PDMCS_DMSI


System Reference of Celerra_PhysicalDataMoverComputerSystem

InstalledSoftware Reference of Celerra_DataMoverSoftwareIdentity

Celerra_InstalledSoftwareIdentity_PCSCS_CSSI

Table 160. Referenced Properties/Methods for Celerra_InstalledSoftwareIdentity_PCSCS_CSSI


System Reference of Celerra_PhysicalControlStationComputerSystem

InstalledSoftware Reference of Celerra_ControlStationSoftwareIdentity

132


133


Physical Package Package

Overview

Physical Package models information about a storage system’s physical package and optionally about internal sub-packages.

A System is realized using a SystemPackaging association to a PhysicalPackage (or subclasses such as Rack and Chassis). The physical containment model can then be built up using Container associations and subclasses (such as ChassisInRack and SlotInChassis).

Physical elements are described as products using the Product class and ProductPhysicalComponent associations. The Product instances may be built up into a hierarchy using the ProductParentChild association. The Product class holds information such as vendor name, serial number and version.

NOTE: For more details, refer to Clause 31: Physical Package Package in Storage Management Technical Specification, Part 2 Common Profiles, Version 1.5.0, Revision 6.

Class Diagram

134


Figure 27. Physical Package Class Diagram


VNX System Product Information

Product Version: Celerra_CelerraProduct.Version.

System Serial Number: Celerra_CelerraProduct.IdentifyingNumber.

System Vendor Name: Celerra_CelerraProduct.Vendor.

Control Station Product Information

Product Version: Celerra_ControlStationProduct.Version.

Control Station Serial Number: Celerra_ ControlStationProduct.IdentifyingNumber.

Control Station Vendor Name: Celerra_ ControlStationProduct.Vendor.

Physical Data Mover Product Information

Product Version: Celerra_CelerraProduct.Version.

Data Mover Serial Number: Celerra_CelerraProduct.IdentifyingNumber.

135


Data Mover Vendor Name: Celerra_CelerraProduct.Vendor.

Storage Processor Product Information

Product Version: Celerra_ClariionSPProduct.Version.

Storage Processor Serial Number: Celerra_ClariionSPProduct.IdentifyingNumber.

Storage Processor Vendor Name: Celerra_ClariionSPProduct.Vendor.

Fiber Channel Adapter Product Information

Product Version: Celerra_DataMoverFCAdapterProduct.Version.

Storage Processor Serial Number: Celerra_DataMoverFCAdapterProduct.IdentifyingNumber.

Storage Processor Vendor Name: Celerra_DataMoverFCAdapterProduct.Vendor.

Ethernet Card Product Information

Product Version: Celerra_DataMoverEthernetCardProduct.Version.

Storage Processor Serial Number: Celerra_DataMoverEthernetCardProduct.IdentifyingNumber.

Storage Processor Vendor Name: Celerra_DataMoverEthernetCardProduct.Vendor.

136


Use Case: Well Defined Subcomponents

For further information, refer to Use Case: Verify Physical Package implementation.

Use Case: Get product information for a ComputerSystem

This use case describes how to get Product information for a ComputerSystem (including Top-level system and subcomponent system):

Use Case: Get Product information for a ComputerSystem

Travers CIM_SystemPackage to CIM_PhysicalPackage

Travers CIM_ProductPhysicalComponent to CIM_Product

Done

CIM_ComputerSystem

Figure 28. Flowchart of getting Product information for ComputerSystem

137


Use Case: Verify Physical Package Implementation

In addition to defining physical packages at the “System” level, PhysicalPackage may also be defined at subcomponent level.

If PhysicalPackage of the subcomponent is modeled, there will be Container relationship between subcomponent physical package (e.g. Data Mover Package) and the containing package (e.g. VNX Package). If Product of the subcomponent is modeled, at the same time, there will be a ProductParentChild association between the subcomponent Product and the parent Product.

Use Case: Verify Physical Package implementationPrecondition: Subcomponents are supported by profile

Check CIM_ProductParentChild Association

Check CIM_Container Association

Travers CIM_Container to CIM_PhysicalPackage(GroupComponent)

to get package of upper system

Verification PassedVerification Failed

Done

CIM_PhysicalPackage for upper system

Travers CIM_ProductPhysicalComponent to

CIM_Product(GroupComponent)

Travers CIM_ProductParentChild to CIM_Product(Parent)

Same Instance

Compare the two results

N Y

CIM_PhysicalPackage for subcomponent

Travers CIM_ProductPhysicalComponent to CIM_Product(GroupComponent) to get

product for subcomponent package

Instance Got

Y

Verification PassedVerification Failed

Same Instance

Compare the two results

N Y

N

Figure 29. Flowchart of Verifying Physical Package Implementation

138


CIM Element

The implemented classes and associations related to the Physical Package in VNX File Storage System can be described as follows:

Table 161. CIM Elements for Physical Package Profile


CIM_CardInSlot

Celerra_CardInSlot_DMS_DMEC

Celerra_CardInSlot_DMS_DMFCA

Associates physical card with the slot where it is plugged.

CIM_Container

Celerra_PackageInChassis_CC_CSC

Celerra_PackageInChassis_CC_DMEEC

Celerra_PackageInChassis_CC_CSPC

Celerra_PackageInChassis_DMEEC_IRC

Celerra_PackageInChassis_DMEEC_DMC

Celerra_PackageInChassis_DMEEC_FM

Celerra_SlotInChassis_DMC_DMS

Associates physical package with its component physical package.

CIM_PhysicalPackage

Celerra_CelerraChassis Physical package for overall VNX File (Celerra) System.

Celerra_ControlStationChassis

Physical package for Control Station component of VNX File.

Celerra_DMEEnclosureChassis

Physical package for DME Enclosure component of VNX File.

Celerra_DataMoverChassis Physical package for Physical Data Mover component of VNX File.

Celerra_ClariionSPChassis Physical package for Storage Processor component of VNX File.

Celerra_InternalRouterChassis

Physical package for Internal Router component of VNX File.

Celerra_DataMoverEthernetCard

Physical package for Data Mover Ethernet Card component of VNX File.

Celerra_DataMoverFCAdapte Physical package for Data Mover Fiber

139


rCard Channel Adapter component of VNX File.

Celerra_BatteryModule Physical package for Battery component of VNX File.

Celerra_FanModule Physical package for Fan component of VNX File.

CIM_Product

Celerra_CelerraProduct Product information for physical package of overall VNX File (Celerra) System.

Celerra_ControlStationProduct

Product information for physical package of Control Station component in VNX File.

Celerra_ClariionSPProduct Product information for physical package of Storage Processor component in VNX File.

Celerra_DMEEnclosureProduct

Product information for physical package of DME Enclosure component in VNX File.

Celerra_DataMoverProduct Product information for physical package of Physical Data Mover component in VNX File.

Celerra_InternalRouterProduct

Product information for physical package of Internal Router component in VNX File.

Celerra_FanProduct Product information for physical package of Fan Module component in VNX File.

Celerra_DataMoverEthernetCardProduct

Product information for physical package of Ethernet card in physical Data Mover.

Celerra_DataMoverFCAdapterProduct

Product information for physical package of fiber channel adapter in physical Data Mover.

CIM_ProductParentChild Celerra_ProductParentChild Associates parent with child product.

CIM_ProductPhysicalComponent

Celerra_ProductPhysicalComponent

Celerra_ProductPhysicalComponent_CP_CC

Celerra_ProductPhysicalComponent_CSP_CSC

Associates a physical package with its product information.

140


Celerra_ProductPhysicalComponent_CSPP_CSPS

Celerra_ProductPhysicalComponent_DMEEP_DMEEC

Celerra_ProductPhysicalComponent_DMP_DMC

Celerra_ProductPhysicalComponent_IRP_IRC

Celerra_ProductPhysicalComponent_FP_FM

Celerra_ProductPhysicalComponent_DMECP_DMEC

Celerra_ProductPhysicalComponent_DMFCACP_DMFCAC

CIM_Slot Celerra_DataMoverSlot Slot of Physical Data Mover.

CIM_SystemPackaging

Celerra_SystemPackaging

Celerra_SystemPackaging_CR_CCS

Celerra_SystemPackaging_CSC_PCSCS

Celerra_SystemPackaging_DMC_PDMCS

Associates a system with its physical package.

Celerra_CelerraChassis

Table 162. Referenced Properties/Methods for Celerra_CelerraChassis


CreationClassName Name of the class used to create this instance.

Tag An arbitrary string that uniquely identifies the physical element as the key of the element.


Module The name by which the physical element is generally known.

SerialNumber A manufacture-allocated number that identifies the physical element.

Manufacture The name of the organization responsible for producing the physical element.

PackageType Type of the PhysicalPackage.

Set to ‘3: Chassis Frame’

141


ChassisPackageType Type of the Chassis.

Set to ’22: Storage Chassis’

Celerra_ControlStationChassis

Table 163. Referenced Properties/Methods for Celerra_ControlStationChassis











Set to ’19: Sub Chassis’

Celerra_DMEEnclosureChassis

Table 164. Referenced Properties/Methods for Celerra_DMEEnclosureChassis








142






Celerra_DataMoverChassis

Table 165. Referenced Properties/Methods for Celerra_DataMoverChassis












Celerra_ClariionSPChassis

Table 166. Referenced Properties/Methods for Celerra_ClariionSPChassis







143







Celerra_InternalRouterChassis

Table 167. Referenced Properties/Methods for Celerra_InternalRouterChassis












Celerra_DataMoverEthernetCard

Table 168. Referenced Properties/Methods for Celerra_DataMoverEthernetCard






144





Set to ‘9: Module Card’

Celerra_DataMoverFCAdapterCard

Table 169. Referenced Properties/Methods for Celerra_DataMoverFCAAdapterCard









Set to ‘9: Module Card’

Celerra_BatteryModule

Table 170. Referenced Properties/Methods for Celerra_BatteryModule







Manufacture The name of the organization responsible for producing the

145


physical element.

Celerra_FanModule

Table 171. Referenced Properties/Methods for Celerra_FanModule









Set to ‘7: Fan’

Celerra_DataMoverSlot

Table 172. Referenced Properties/Methods for Celerra_DataMoverSlot





Celerra_CelerraProduct

Table 173. Referenced Properties/Methods for Celerra_CelerraProduct


Name The name of the product.

Vendor The name of the product’s supplier.

Version The version of the product.

IdentifyingNumber Product identification.

146




Celerra_ControlStationProduct

Table 174. Referenced Properties/Methods for Celerra_ControlStationProduct








Celerra_DMEEnclosureProduct

Table 175. Referenced Properties/Methods for Celerra_DMEEnclosureProduct








Celerra_ClariionSPProduct

Table 176. Referenced Properties/Methods for Celerra_ClariionSPProduct





147





Celerra_DataMoverProduct

Table 177. Referenced Properties/Methods for Celerra_DataMoverProduct








Celerra_InternalRouterProduct

Table 178. Referenced Properties/Methods for Celerra_InternalRouterProduct








Celerra_DataMoverEthernetCardProduct

Table 179. Referenced Properties/Methods for Celerra_DataMoverEthernetCardProduct




148






Celerra_DataMoverFCAdapterProduct

Table 180. Referenced Properties/Methods for Celerra_DataMoverFCAdapterProduct








Celerra_SystemPackaging_CC_CCS

Table 181. Referenced Properties/Methods for Celerra_SystemPackaging_CC_CCS


Antecedent Reference of Celerra_CelerraChassis

Dependent Reference of Celerra_CelerraComputerSystem

Celerra_SystemPackaging_CSC_PCSCS

Table 182. Referenced Properties/Methods for Celerra_SystemPackaging_CSC_PCSCS


Antecedent Reference of Celerra_ControlStationChassis

Dependent Reference of Celerra_PhysicalControlStationComputerSystem

Celerra_SystemPackaging_DMC_PDMCS

Table 183. Referenced Properties/Methods for Celerra_SystemPackaging_DMC_PDMCS


149


Antecedent Reference of Celerra_DataMoverChassis

Dependent Reference of Celerra_PhysicalDataMoverComputerSystem

Celerra_ProductPhysicalComponent_CP_CC

Table 184. Referenced Properties/Methods for Celerra_ProductPhysicalComponent_CP_CC


GroupComponent Reference of Celerra_CelerraProduct

PartComponent Reference of Celerra_CelerraChassis

Celerra_ProductPhysicalComponent_CSP_CSC

Table 185. Referenced Properties/Methods for Celerra_ProductPhysicalComponent_CSP_CSC


GroupComponent Reference of Celerra_ControlStationProduct

PartComponent Reference of Celerra_ControlStationChassis

Celerra_ProductPhysicalComponent_CSPP_CSPS

Table 186. Referenced Properties/Methods for Celerra_ProductPhysicalComponent_CSPP_CSPS


GroupComponent Reference of Celerra_ClariionSPProduct

PartComponent Reference of Celerra_ClariionSPChassis

Celerra_ProductPhysicalComponent_DMEEP_DMEEC

Table 187. Referenced Properties/Methods for Celerra_ProductPhysicalComponent_DMEEP_DMEEC


GroupComponent Reference of Celerra_DMEEnclosureProduct

PartComponent Reference of Celerra_DMEEnclosureChassis

Celerra_ProductPhysicalComponent_DMP_DMC

Table 188. Referenced Properties/Methods for Celerra_ProductPhysicalComponent_DMP_DMC


GroupComponent Reference of Celerra_DataMoverProduct

150


PartComponent Reference of Celerra_DataMoverChassis

Celerra_ProductPhysicalComponent_IRP_IRC

Table 189. Referenced Properties/Methods for Celerra_ProductPhysicalComponent_IRP_IRC


GroupComponent Reference of Celerra_InternalRouterProduct

PartComponent Reference of Celerra_InternalRouterChassis

Celerra_ProductPhysicalComponent_FP_FM

Table 190. Referenced Properties/Methods for Celerra_ProductPhysicalComponent_FP_FM


GroupComponent Reference of Celerra_FanProduct

PartComponent Reference of Celerra_FanModule

Celerra_ProductPhysicalComponent_DMECP_DMEC

Table 191. Referenced Properties/Methods for Celerra_ProductPhysicalComponent_DMEEP_DMEEC


GroupComponent Reference of Celerra_DataMoverEthernetCardProduct

PartComponent Reference of Celerra_DataMoverEthernetCard

Celerra_ProductPhysicalComponent_DMFCACP_DMFCAC

Table 192. Referenced Properties/Methods for Celerra_ProductPhysicalComponent_DMFCACP_DMFCAC


GroupComponent Reference of Celerra_DataMoverFCAdapterCardProduct

PartComponent Reference of Celerra_DataMoverFCAdapterCard

Celerra_PackageInChassis_CC_CSC

Table 193. Referenced Properties/Methods for Celerra_PackageInChassis_CC_CSC


GroupComponent Reference of Celerra_CelerraChassis

151


PartComponent Reference of Celerra_ControlStationChassis

Celerra_PackageInChassis_CC_DMEEC

Table 194. Referenced Properties/Methods for Celerra_PackageInChassis_CC_DMEEC



PartComponent Reference of Celerra_DMEEnclosureChassis

Celerra_PackageInChassis_CC_CSPC

Table 195. Referenced Properties/Methods for Celerra_PackageInChassis_CC_CSPC



PartComponent Reference of Celerra_ClariionSPChassis

Celerra_PackageInChassis_DMEEC_IRC

Table 196. Referenced Properties/Methods for Celerra_PackageInChassis_DMEEC_IRC


GroupComponent Reference of Celerra_DMEEnclosureChassis

PartComponent Reference of Celerra_InternalRouterChassis

Celerra_PackageInChassis_DMEEC_DMC

Table 197. Referenced Properties/Methods for Celerra_PackageInChassis_DMEEC_DMC



PartComponent Reference of Celerra_DataMoverChassis

Celerra_PackageInChassis_DMEEC_FM

Table 198. Referenced Properties/Methods for Celerra_PackageInChassis_DMEEC_FM



PartComponent Reference of Celerra_FanModule

152


Celerra_ProductParentChild_CP_CSP

Table 199. Referenced Properties/Methods for Celerra_PackageInChassis_CP_CSP


Parent Reference of Celerra_CelerraProduct

Child Reference of Celerra_ControlStationProduct

Celerra_ProductParentChild_CP_CSPP

Table 200. Referenced Properties/Methods for Celerra_PackageInChassis_CP_CSPP



Child Reference of Celerra_ClariionSPProduct

Celerra_ProductParentChild_CP_DMEEP

Table 201. Referenced Properties/Methods for Celerra_PackageInChassis_CP_DMEEP



Child Reference of Celerra_DMEEnclosureProduct

Celerra_ProductParentChild_DMEEP_DMP

Table 202. Referenced Properties/Methods for Celerra_PackageInChassis_DMEEP_DMP


Parent Reference of Celerra_DMEEnclosureProduct

Child Reference of Celerra_DataMoverProduct

Celerra_ProductParentChild_DMEEP_IRP

Table 203. Referenced Properties/Methods for Celerra_PackageInChassis_DMEEP_IRP



Child Reference of Celerra_InternalRouterProduct

Celerra_ProductParentChild_DMEEP_FP

Table 204. Referenced Properties/Methods for Celerra_PackageInChassis_DMEEP_FP

153




Child Reference of Celerra_FanProduct

Celerra_SlotInChassis_DMC_DMS

Table 205. Referenced Properties/Methods for Celerra_SlotInChassis_DMC_DMS


GroupComponent Reference of Celerra_DataMoverChassis

PartComponent Reference of Celerra_DataMoverSlot

Celerra_CardInSlot_DMS_DMEC

Table 206. Referenced Properties/Methods for Celerra_CardInSlot_DMS_DMEC


Antecedent Reference of Celerra_DataMoverSlot

Dependent Reference of Celerra_DataMoverEthernetCard

Celerra_CardInSlot_DMS_DMFCAC

Table 207. Referenced Properties/Methods for Celerra_CardInSlot_DMS_DMFCAC


Antecedent Reference of Celerra_DataMoverSlot

Dependent Reference of Celerra_DataMoverFCAdapterCard

154


Health Package

Overview

Failures and abnormal occurrences are common in monitoring, controlling, and configuring devices and applications. An SMI-S client needs to be prepared at all times to trap unexpected situations and take appropriate action. This package defines the general mechanisms used in the expression of health in SMI-S. This package does not define the particular ways to report the state of health.

NOTE: For more details, refer to Clause 25: Health Package in Storage Management Technical Specification, Part 2 Common Profiles, Version 1.5.0, Revision 6.

Class Diagram

N/A


N/A

CIM Element

N/A

155


Indication Profile

Overview

The Indication Profile is a component profile of the Server Profile. It may also be a component profile of any other profile, for example, Array Profile. The Indication Profile allows a client to be notified when a particular event occurs.

NOTE: For more details, refer to Clause 42: Indication Profile in Storage Management Technical Specification, Part 2 Common Profiles, Version 1.5.0, Revision 6.

Class Diagram

Figure 30. Indication Class Diagram


Indication Filter and Handler

In VNX SMI-S provider, indication filter and handler are intended to originate in Interop namespace. Both pre-defined and client-defined indication filters are supported.

Table 208. Supported Pre-defined Indication Filters

Indication Name Query

SPCreation SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_StoragePool

SPDeletion SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA

156


CIM_StoragePool

SPModification SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_StoragePool

FSCreation SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA SNIA_LocalFileSystem

FSModification SELECT * FROM CIM_InstModification WHERE SourceInstance ISA SNIA_LocalFileSystem

FileShareCreation SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_FileShare

FileShareDeletion SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_FileShare

NOTE: To receive the other specified indications, client is required to create/define indication filter and handler and subscribe them using IndicationSubscription.

PreviousInstance Support

PreviousInstance of InstModification is not supported by SMI-S Provider on VNX for File.

Indication Support

SMI-S Provider on VNX for File supports both Alert indications and Life cycle indications on the following CIM objects.

Table 209. Supported Life Cycle Indications

CIM Object Life Cycle Indication Support

Celerra_UxfsLocalFileSystem

CIM_InstCreation Y

CIM_InstDeletion Y

CIM_InstModification Y

Celerra_LogicalDisk

CIM_InstCreation Y

CIM_InstDeletion Not Supported


Celerra_CompositeExtent

CIM_InstCreation Y



Celerra_NonPrimordialStorageExtent

CIM_InstCreation Y




CIM_InstCreation Y



Celerra_CIFSShare

CIM_InstCreation Y

CIM_InstDeletion Y


157


Celerra_NFSShare

CIM_InstCreation Y

CIM_InstDeletion Y



CIM_InstCreation Y

CIM_InstDeletion Y



CIM_InstCreation Y

CIM_InstDeletion Y


Celerra_CIFSServer

CIM_InstCreation Y

CIM_InstDeletion Y


Celerra_NFSServer

CIM_InstCreation Y

CIM_InstDeletion Y


NOTE: In the current release, CIM_InstDeletion indications for Celerra_LogicalDisk, Celerra_CompositeExtent, Celerra_NonPrimordialStorageExtent, Celerra_PrimordialStorageExtent are not sent out since backend component only provided volume ID for volume deletion. It is not sufficient for SMI-S provider to obtain volume type and composite topology information to convert volume objects to corresponding SMI-S models.

Indication Trigger

Manipulation on NAS object via SMI-S Provide, Unisphere GUI or NAS CLI will trigger SMI-S Provider to send out corresponding indication or various types of indications.

Create/Delete FileSystem from StoragePool

FileSystem creation/deletion/modification may trigger CIM_InstCreation/CIM_InstDeletion/ CIM_Modification for the FileSystem. At the same time, volumes change along with the FileSystem operation which is transparent to client. Corresponding indications for Celerra_LogicalDisk, Celerra_CompositExtent, Celerra_NonPrimordialStorageExtent or Celerra_PrimordialStorageExtent may be sent out as well.

Rename Data Mover/Virtual Data Mover

Rename Data Mover/VDM may trigger CIM_InstDeletion and CIM_InstCreation for objects including the Data Mover/VDM, all File Servers on the Data Mover/VDM, and all File Shares/Exports exported from these File Servers.

Rename File Server

Rename File Server may trigger CIM_InstDeletion and CIM_InstCreation for objects including the File Server, and all File Shares/Exports exported from the File Servers.

Use Case: CQL for Celerra Profiles

CIM Server and ObjectManager (ECOM) on VNX for File supports the stand of DMTF:CQL for indication

query. For more details, refer to "DMTF: CIM Query Language Specification(DSP0202)".

http://www.dmtf.org/sites/default/files/standards/documents/DSP0202_1.0.0.pdf

158


Use Case: Creation of IndicationFilter and ListenerDestination Instances

Invoke intrinsic method CreateInstance on IndicationFilter and ListenerDestinationCIMXML to create client-defined filter and handler.

For further information, refer to Use Case: Subscribe Indication using Client-Defined Filters.

Use Case: Determine if the indication subscription requested already exists

For further information, refer to Use Case: Subscript Indication using Client-Defined Filters.

Use Case: Creation of IndicationSubscription Instances

Invoke intrinsic method CreateInstance on IndicationSubscription to subscribe indication.

For further information, refer to Use Case: Subscribe Indication using Client-Defined Filters.

159


Use Case: Subscribe Indication using client-defined filters

The following example describes how to

1) Create a Client-Defined Indication Filter (instance of IndicationFilter); 2) Create an Indication handler (the instance of ListenerDestinationCIMXML); 3) Create the IndicationSubscription (if not exist) with the Filter and Handler.

After subscription, client should listen to the URL filled in ListenerDestinationCIMXML.Destination to receive specified indications filtered by the Client-Defined Filter.

Use Case: Subscribe Indication using Client-defined Filter

Subscribe Indication

Create Handler

Create Filter

Invoke CreateInstance on CIM_IndicationFilter

Invoke CreateInstance on CIM_ListenerDestinationCIMXML

Invoke CreateInstance on CIM_IndicationSubscription

Start

Connect to interop namespace

Required Input Properties Name Query QueryLanguage SourceNamspace

Required Input Properties Name Destination

Required Input Properties Filter Handler

Input

Input

Input

Filter

Handler

Done

Figure 31. Flowchart of Indication Subscription

CIM Element

The implemented classes and associations related to the Physical Package Profile in VNX File Storage System can be described as follows:

Table 210. CIM Element in Indication Profile


CIM_AlertIndication CIM_AlertIndication Used to capture events occurred in VNX File System.

160


CIM_InstCreation CIM_InstCreation An indication of the creation of a CIM instance.

CIM_InstDeletion CIM_InstDeletion An indication of the deletion of a CIM instance.

CIM_InstModification CIM_InstModification An indication of the modification of a CIM instance.

CIM_IndicationFilter EMC_IndicationFilter (pre-defined)

A system 'pre-defined' filter that defines the value and the format of an indication filter string.

CIM_IndicationFilter EMC_IndicationFilter (client-defined)

A client defined filter that defines the value and the format of an indication filter string.

CIM_IndicationSubscription EMC_IndicationSubscription

Defines a subscription to a specific IndicationFilter instance by a specific indication handler (as represented by a ListenerDestinationCIMXML instance).

CIM_ListenerDestinationCIMXML

EMC_ListenerDestinationCIMXML

The destination for CIM Export Messages to be delivered via CIM-XML.

CIM_AlertIndication

Table 211. Referenced Properties/Methods for CIM_AlertIndication



AlertingManagedElement Information of the entity for which this indication is generated.

AlertingElementFormat Format of the AlertingManagedElement property.

IndicationTime The time and data of creation of the indication.

AlertType Primary classification of the indication.

OtherAlertType Additional information that describes the AlertType when AlertType is set to {1: Other State Change}.

EventID Provider specified value that describes the underlying system event.

PerceivedSeverity Severity of the Alert Indication from the notifier’s point of view.

OtherSeverity Value of the user-defined severity when PerceivedSeverity is set to {1: Other}.

161


ProbableCauseDescription Additional information related to the ProbableCause.

ProbableCause Probable cause of the situation which resulted in the AlertIndication.

Trending Information on trending.

CIM_InstCreation

Table 212. Referenced Properties/Methods for CIM_InstCreation



SourceInstance A copy of the instance that changed to generate the Indication. SourceInstance contains the current values of the properties selected by the Indication Filter's Query.

SourceInstanceModelPath The Model Path of the SourceInstance.

CIM_InstDeletion

Table 213. Referenced Properties/Methods for CIM_InstDeletion





CIM_InstModification

Table 214. Referenced Properties/Methods for CIM_InstModification





EMC_IndicationFilter

Table 215. Referenced Properties/Methods for EMC_IndicationFilter


162





Name Name of the filter

Query A query expression that defines the condition under which indication will be generated.

QueryLanguage The language in which the query is expressed.

SourceNamespace The path to a local namespace where the indication originate.

EMC_ListenerDestinationCIMXML

Table 216. Referenced Properties/Methods for EMC_ListenerDestinationCIMXML





Name Name of the filter

Destination The destination URL to which CIM-XML Export Messages are to be delivered.

EMC_IndicationSubscription

Table 217. Referenced Properties/Methods for EMC_IndicationSubscription


Filter Reference of EMC_IndicationFilter

Handler Reference of EMC_ListenerDestinationCIMXML

163


Location Profile

Overview

Associated with product information, a PhysicalPackage may also have a location. This is indicated using an instance of a Location class and the PhysicalElementLocation association.

NOTE: For more details, refer to Clause 25: Location Subprofile in Storage Management Technical Specification, Part 2 Common Profiles, Version 1.5.0, Revision 6.

Class Diagram

Figure 32. Location Class Diagram

164



N/A

CIM Element

The implemented classes and associations related to the Location Profile in VNX File Storage System can be described as follows:

Table 218. CIM Elements for Location Profile


CIM_Location Celerra_Location Location of a physical element.

CIM_PhysicalElementLocation

Celerra_PhysicalElementLocation

Celerra_PhysicalElementLocation_CC_L

Celerra_PhysicalElementLocation_CSC_L

Celerra_PhysicalElementLocation_CSPC_L

Celerra_PhysicalElementLocation_DMEEC_L

Celerra_PhysicalElementLocation_DMC_L

Celerra_PhysicalElementLocation_DMFCAC_L

Celerra_PhysicalElementLocation_DMEC_L

Celerra_PhysicalElementLocation_DMS_L

Celerra_PhysicalElementLocation_IRC_L

Celerra_PhysicalElementLocation_FM_L

Associates the location with the physical element.

Celerra_Location

Table 219. Referenced Properties/Methods for Celerra_Location


Name A free-form string defining label of the location.

PhysicalPosition A free-form string indicating the placement of the PhysicalElement.

165



Celerra_PhysicalElementLocation_CC_L

Table 220. Referenced Properties/Methods for Celerra_PhysicalElementLocation_CC_L


Element Reference of Celerra_CelerraChassis

PhysicalLocation Reference of Celerra_Location

Celerra_PhysicalElementLocation_CSC_L

Table 221. Referenced Properties/Methods for Celerra_PhysicalElementLocation_CSC_L


Element Reference of Celerra_ControlStationChassis


Celerra_PhysicalElementLocation_CSPC_L

Table 222. Referenced Properties/Methods for Celerra_PhysicalElementLocation_CSPC_L


Element Reference of Celerra_ClariionSPChassis


Celerra_PhysicalElementLocation_DMEEC_L

Table 223. Referenced Properties/Methods for Celerra_PhysicalElementLocation_DMEEC_L


Element Reference of Celerra_DMEEnclosureChassis


Celerra_PhysicalElementLocation_DMC_L

Table 224. Referenced Properties/Methods for Celerra_PhysicalElementLocation_DMC_L


Element Reference of Celerra_DataMoverChassis


166


Celerra_PhysicalElementLocation_DMFCA_L

Table 225. Referenced Properties/Methods for Celerra_PhysicalElementLocation_DMFCAC_L


Element Reference of Celerra_DataMoverFCAdapterCard


Celerra_PhysicalElementLocation_DMEC_L

Table 226. Referenced Properties/Methods for Celerra_PhysicalElementLocation_DMEC_L


Element Reference of Celerra_DataMoverEthernetCard


Celerra_PhysicalElementLocation_DMS_L

Table 227. Referenced Properties/Methods for Celerra_PhysicalElementLocation_DMS_L


Element Reference of Celerra_DataMoverSlot


Celerra_PhysicalElementLocation_IRC_L

Table 228. Referenced Properties/Methods for Celerra_PhysicalElementLocation_IRC_L


Element Reference of Celerra_InternalRouterChassis


Celerra_PhysicalElementLocation_FM_L

Table 229. Referenced Properties/Methods for Celerra_PhysicalElementLocation_FM_L


Element Reference of Celerra_FanModule


167


File Server Manipulation Profile

Overview

The File Server Manipulation Subprofile is a subprofile of autonomous profiles that support file systems. It utilizes the elements of the file system subprofiles and supports creation and deletion of Virtual File Servers and the modification of both virtual and non-virtual File Servers. A number of the other profiles and subprofiles also make use of elements of the File System subprofile and will be referred to this specification as “File System-related profiles” -- these include, but are not limited to, the File System subprofile, the File System Manipulation Subprofile, the File Export Subprofile, the NAS Head Profile, the Self-Contained NAS Profile.

A File Server is a computer system that is attached to a network and provides resources to allow client systems to access to file system resources in the form of CIFS Shares and/or NFS Exports. A File Server can be either a physical computer system or a virtual system that is hosted by a physical computer system. A physical File Server can neither be created nor deleted but may have properties that can be modified via configuration actions. A virtual File Server can be created, deleted, and modified via configuration actions. This profile models both physical and virtual File Servers.

NOTE: In VNX for File, supported File Servers are all virtual servers.

Extrinsic methods are provided for the creation and deletion of virtual File Servers. Extrinsic methods are also provided for the modification of properties in both physical and virtual File Servers. According to SNIA SMI-S specification, the implementation can provide either a read-only view of the File Servers or may provide extrinsic methods for configuring existing and/or new File Servers. A client can determine if a read-only implementation is provided by inspecting the two FileServerConfigurationCapabilities arrays SynchronousMethodsSupported and AsynchronousmethodsSupported. If they are both empty or null, then the implementation is read-only.

NOTE: In VNX for File, the File Server Manipulation Profile is a Read-Only implementation.

This profile supports viewing and configuring the following property “areas” of a File Server:

NFS Exports

CIFS Shares

Ethernet port properties including VLAN tagging.

DNS Settings

NIS Settings

NOTE: For more details, refer to Clause 6: File Server Manipulation Profile in Storage Management Technical Specification, Part 4 Filesystems Version 1.6.0, Revision 4.

168


Class Diagram

Figure 33. File Server Manipulation Class Diagram


Supported File Server

All File Servers (NFS or CIFS) in VNX are virtual.

NFS File Server is only supported by Data Mover instead of Virtual Data Mover and there can be only one NFS File Server per Data Mover.

CIFS File Server is supported by Data Mover and Virtual Data Mover. There is no explicit limitation on the number of CIFS Server.

File Server Manipulation

VNX SMI-S Provider provides a Read-Only implementation of File Server Manipulation Profile.

Client can determine if a read-only implementation is provided by inspecting the two arrays FileServerConfigurationCapabilities.SynchronousMethodsSupported and FileServerConfigurationCapabilities.AsynchronousmethodsSupported. If they are both empty or null, then the implementation is read-only.

Client can manage File Servers via Unisphere GUI or NAS CLI.

Operational Status for File Server ComputerSystem

Implemented in Celerra_CIFSServer.OperationalStatus and Celerra_NFSServer.OperationalStatus.

169


File Server Setting Data

Client can retrieve setting data for a File Server via the following classes.

CIFS Setting Data (Celerra_CIFSSettingData)

Table 230. CIFS Setting Data

Property Description

Enabled If CIFS is supported by the File Server or not.

NETBIOSName The netbios name for the File Server.

AuthenticationDomain Authentication domain for the File Server.

AuthenticationMode Authentication mode for the File Server.

MultiChannelSupported If multi-channel is supported by the File Server or not.

CASupported If Continuous Availability (CA) is supported by the File Server or not.

ProtocolVersions Supported SMB version.

NFS Setting Data (Celerra_NFSSettingData)

Table 231. NFS Setting Data


Enabled If NFS is supported by the File Server or not.

Port Port for NFS access.

DNS Setting Data (Celerra_DNSSettingData)

Table 232. DNS Setting Data


DomainName Name of the domain that the File Server joined.

DNSServerAddress Address of the DNS server.

NIS Setting Data (Celerra_NISSettingData)

Table 233. NIS Setting Data


DomainName NIS domain.

ServerIP NIS server IP.

IP Interface Setting Data (Celerra_IPInterfaceSettingData)

Table 234. IP Interface Setting Data


IPAddress Address of the IP interface.

AddressType Format of the IP address.

SubnetMask Subnet mask.

170


RSSCapable If RSS is capable for the interface or not.

RDMACapable If RDMA is capable for the interface or not.

LinkSpeed Link speed of the interface.

Use Case: Determine if a Read-Only implementation is provided

Client can determine if a read-only implementation is provided by inspecting the two arrays FileServerConfigurationCapabilities.SynchronousMethodsSupported and FileServerConfigurationCapabilities.AsynchronousmethodsSupported. If they are all empty or null, then the implementation is read-only.

CIM Element

The implemented classes and associations related to the File Server Manipulation Profile in VNX File can be described as follows:

Table 235. CIM Elements for File Server Manipulation Profile


CIM_ConcreteComponent

Celerra_ConcreteComponent_FSS_CIFSSD

Celerra_ConcreteComponent_FSS_NFSSD

Celerra_ConcreteComponent_FSS_DNSSD

Celerra_ConcreteComponent_FSS_NISSD

Celerra_ConcreteComponent_FSS_IPISD

Associates FileServerSettings element with the concrete setting data elements including CIFS, NFS, DNS, NIS and IP Interface.

CIM_DNSSettingData Celerra_DNSSettingData DNS setting data to be used by the File Server.

CIM_ElementCapabilities Celerra_ElementCapabilities_FSrvCS_FSC

Associates File Server Configuration Service with the Capabilities element that represents capabilities supported by all File Servers.

CIM_ElementCapabilities Celerra_ElementCapabilities_FSrvCS_FSCC

Associates File Server Configuration Service with the ConfigurationCapabilities element that represents capabilities that it supports.

CIM_HostedService_CCS_FSrvCS

Celerra_HostedService_CCS_FSrvCS

Associates the ConfigurationService with its scoping system (NAS Head).

CIM_SettingsDefineState

Celerra_SettingsDefineState_NFSS_FSS

Associates the FileServer ComputerSystem (CIFS and NFS) with its FileServerSettings element that

171


Celerra_SettingsDefineState_CIFSS_FSS

represents the state of the File Server.

SNIA_FileServerCapabilites Celerra_FileServerCapabilities

Capabilities of the File Server.

SNIA_FileServerConfigurationCapabilities

Celerra_FileServerConfigurationCapabilities

Represents the management Capabilities of the File Server Configuration Service.

SNIA_FileServerConfigurationService

Celerra_FileServerConfigurationService

Provides methods for File Server management.

SNIA_FileServerSettings Celerra_FileServerSettings Settings for the File Server.

SNIA_CIFSSettingData Celerra_CIFSSettingData CIFS settings for the File Server.

SNIA_IPInterfaceSettingData Celerra_IPInterfaceSettingData

IP interface setting data for the File Server.

SNIA_NFSSettingData Celerra_NFSSettingData NFS settings for the File Server.

SNIA_NISSettingData Celerra_NISSettingData NIS settings for the File Server.

Celerra_FileServerConfigurationService

Table 236. Referenced Properties/Methods for Celerra_FileServerConfigurationService





Name Name of the instance.


Celerra_FileServerConfigurationCapabilities

Table 237. Referenced Properties/Methods for Celerra_FileServerConfigurationCapabilities




CanConfigureNFS Whether NFS settings can be configured.

CanConfigureCIFS Whether CIFS settings can be configured.

172


CanConfigureNIS Whether NIS settings can be configured.

CanConfigureDNS Whether DNS settings can be configured.

CanConfigureNetworkVLAN Whether Network VLAN tagging settings can be configured.

SynchronousMethodsSupport An array of methods of the service that are supported as synchronous methods.

AsynchronousMethodsSupport An array of methods of the service that are supported as asynchronous methods.

Celerra_FileServerCapabilites

Table 238. Referenced Properties/Methods for Celerra_FileServerCapabilities




NFSSupported Whether the File Server ComputerSystem supports NFS.

CIFSSupported Whether the File Server ComputerSystem supports CIFS.

NISSupported Whether the File Server ComputerSystem supports NIS.

DNSSupported Whether the File Server ComputerSystem supports DNS.

NetworkVLANSupported Whether the File Server ComputerSystem supports Network VLAN tagging.

FileServerSettingsSupported Whether there will be a FileServerSettings instance associated with the File Server.

Celerra_FileServerSettings

Table 239. Referenced Properties/Methods for Celerra_FileServerSettings




Celerra_CIFSSettingData

Table 240. Referenced Properties/Methods for Celerra_CIFSSettingData


173



Enabled If CIFS is supported by the File Server.

NETBIOSName The netbios name for the File Server.

AuthenticationDomain Authentication domain for the File Server.

AuthenticationMode Authentication mode for the File Server.

MultiChannelSupported If multi-channel is supported by the File Server.

CASupported If Continuous Availability (CA) is supported by the File Server.

ProtocolVersions Supported SMB version.

Celerra_NFSSettingData

Table 241. Referenced Properties/Methods for Celerra_



Enabled If NFS supported by the File Server.

Port Port for NFS access.

Celerra_DNSSettingData




DomainName Name of the domain the File Server joined.

DNSServerAddress Address of the DNS server.

Celerra_NISSettingData




DomainName NIS domain.

ServerIP NIS server IP.

174


Celerra_IPInterfaceSettingData

For further information, refer to Celerra_IPInterfaceSettingData in NAS Network Port Profile.

Celerra_HostedService_CCS_FSrvCS

Table 244. Referenced Properties/Methods for Celerra_HostedService_CCS_FSrvCS



Dependent Reference of Celerra_FileServerConfigurationService

Celerra_ElementCapabilities_FSrvCS_FSC

Table 245. Referenced Properties/Methods for Celerra_ElementCapabilities_FSrvCS_FSC


ManagedElement Reference of Celerra_FileServerConfigurationService

Capabilities Reference of Celerra_FileServerCapabilities

Celerra_ElementCapabilities_FSrvCS_FSCC

Table 246. Referenced Properties/Methods for Celerra_ElementCapabilities_FSrvCS_FSCS


ManagedElement Reference of Celerra_FileServerConfigurationService

Capabilities Reference of Celerra_FileServerConfigurationCapabilities

Celerra_SettingsDefineState_NFSS_FSS

Table 247. Referenced Properties/Methods for Celerra_SettingsDefineState_NFSS_FSS


ManagedElement Reference of Celerra_NFSServer

SettingData Reference of Celerra_FileServerSettings

Celerra_SettingsDefineState_CIFSS_FSS

Table 248. Referenced Properties/Methods for Celerra_SettingsDefineState_CIFSS_FSS


ManagedElement Reference of Celerra_CIFSServer

SettingData Reference of Celerra_FileServerSettings

175


Celerra_ConcreteComponent_FSS_CIFSSD

Table 249. Referenced Properties/Methods for Celerra_ConcreteComponent_FSS_CIFSSD


GroupComponent Reference of Celerra_FileServerSettings

PartComponent Reference of Celerra_CIFSSettingData

Celerra_ConcreteComponent_FSS_NFSSD

Table 250. Referenced Properties/Methods for Celerra_ConcreteComponent_FSS_NFSSD



PartComponent Reference of Celerra_NFSSettingData

Celerra_ConcreteComponent_FSS_DNSSD

Table 251. Referenced Properties/Methods for Celerra_ConcreteComponent_FSS_DNSSD



PartComponent Reference of Celerra_DNSSettingData

Celerra_ConcreteComponent_FSS_NISSD

Table 252. Referenced Properties/Methods for Celerra_ConcreteComponent_FSS_NISSD



PartComponent Reference of Celerra_NISSettingData

Celerra_ConcreteComponent_FSS_IPISD

Table 253. Referenced Properties/Methods for Celerra_ConcreteComponent_FSS_IPISSD



PartComponent Reference of Celerra_IPInterfaceSettingData

176


Simple Identity Management Profile

Overview

The Simple Identity Management Profile provides the ability of representing a principal with a User ID that has been authenticated through the third-party authentication, and managing the privilege of the account for the exported CIFS File Share.

Class Diagram

Figure 34. Simple Identity management Class Diagram


Celerra_UserContact

Class Celerra_UserContact represents account information about an identity that has been authenticated through a third-party authentication (Active Directory in VNX File).

NOTE: Creation/Deletion of a UserContact via SMI-S Provider does not literally add or remove the corresponding account in the Active Directory. This operation only enables the share access privilege of the account to be manageable or unmanageable by the SMI-S Provider.

Celerra_Identity

Class Celerra_Identity represents the SID of an account on Active Directory.

NOTE: Client cannot manipulate Identity directly via SMI-S Provider. Identity can only be affected by UserContact manipulation.

Celerra_AssociatePrivilege_CIFSS_IDY

Since VNX File applied ACL (Access Control List) for CIFS Share access, class Celerra_AssociatePrivilege_CIFSS_IDY represents the ACE (Access Control Entry) on a pair of Identity and CIFS File Share.

177


Table 254. Associated Privilege


Subject The Identity for which the privilege has been granted or denied.

Target The CIFS Share to which the privilege has been applied.

Activities The activities granted or denied.

PrivilegeGranted Indicates whether the privilege is granted of denied.

NOTE: Property PrivilegeGranted is always set to TRUE as SMI-S only supports privilege granting and only exposes granted ACEs.

Mapping between Activities and Privileges in ACE can be described as follows:

Table 255. Activities and Privileges Mapping

Activities Set By Client Activities Shown In SMI-S Privileges To Share

Client input contains {5:Read, 6:Write, 14: Authorize to Grant/Deny Authorization}.

{2: Create, 3: Delete, 5, 6, 7:Execute, 14}

FULLCONTROL

Client input contains {5, 6} but does not contain {14}.

{2, 3, 5, 6, 7} CHANGE

Client input contains {5} but does not contain {6, 14}.

{5, 7} READ

Client input contains none of the values in {5, 6, 14}

ERROR, Not Supported, Invalid

ERROR, Not Supported, Invalid

UserContact Manipulation

List UserContact

Implemented by intrinsic method EnumerateInstances of Celerra_UserContact.

NOTE: It is NOT recommended to directly invoke this method to list all existing UserContacts in SMI-S. Alternatively, the user should invoke the method Celerra_AccountManagementService.getUserContact to retrieve UserContact for specific domain user.

NOTE: A UserContact can be listed if the following conditions are satisfied:

1) The UserContact has been explicitly created by the client via SMI-S.

2) The corresponding account exists in Active Directory.

3) The communication between VNX for File and Active Directory is active.

Retrieve UserContact

Implemented by extrinsic method Celerra_AccountManagementService.getUserContact.

Signature and Parameters of the method are described as follows:

Table 256. Signature and Parameters of getUserContact


UserID IN, Required A string includes domain and user name for retrieving UserContact. It should be in the format: “Domain\UserName”

178


UserContact OUT Reference of the target UserContact.

NOTE: A UserContact can be retrieved by UserID if the following conditions are satisfied:

1) The UserContact has been explicitly created by the client via SMI-S.



Create UserContact

Implemented in extrinsic method Celerra_AccountManagementService.CreateUserContact.


Table 257. Signature and Parameters of CreateUserContanct


System IN, Required The scoping system in which the UserContact is managed.

UserContactTemplate IN, Required An embedded instance of Celerra_UserContact containing domain and user information for creation.

UserContact OUT Reference of the newly created UserContact.

Identities OUT An array of references of Identity associated the newly created UserContact.

NOTE: A UserContact can be created in SMI-S if the following conditions are satisfied:

1) The UserContact has not been created yet. Client cannot create a UserContact for twice.



Delete UserContact

Implemented by intrinsic method DeleteInstance of Celerra_UserContact.

NOTE: Deletion of a UserContact will remove all privileges assigned to all Identities associated with the UserContact at the same time. As a result, all share access privileges of the account on Active Directory will be removed if the UserContact in SMI-S for this account has been removed.

Privilege Manipulation

List Privileges on a given File Share

Intrinsic method References of Celerra_CIFSShare will return all ACEs on the given File Share.

NOTE: It is NOT recommended to directly invoke the intrinsic method EnumerateInstances of Celerra_AssociatedPrivilege_CIFSS_IDY to list all existing ACEs.

NOTE: An ACE will be exposed to SMI-S client if the following conditions are satisfied:

1) Permission of the ACE has been granted rather than denied. SMI-S only displays granted permission.

2) The UserContact associated with the Identity has been created in SMI-S.

3) Account whose SID is represented by the Identity exists in Active Directory.


179


Assign Privilege

Implemented by extrinsic method Celerra_FileExportService.AssignPrivilegeOnExportedShare.


Table 258. Signature and Parameters of AssignPrivilegeOnExportedShare


Identities IN, Required An array of Identities for which the privilege will be granted.

FileShare IN, Required The CIFS Share to which the privilege will be applied.

Activities IN, Required An array of activities to be granted for the input Identities to the input FileShare.

NOTE: Privilege can be assigned successfully if the following conditions are satisfied:

1) Accounts whose SIDs are represented by the Identities exist in Active Directory.

2) Value of Activities is valid to VNX SMI-S Provider (see Activities Mapping).

3) Privileges that haven be assigned should NOT exist. Client cannot assign the same privilege to a CIFS Share twice.


Remove Privilege

Implemented by intrinsic method DeleteInstance of Celerra_AssociatedPrivilege_CIFSS_IDY.

Modify Privilege

Implemented in intrinsic method ModifyInstance of Celerra_AssociatedPrivilege_CIFSS_IDY.

NOTE: Only property Activities is allowed to be modified, and the value should follow the convention in Activities Mapping.

180


Use Case: Create UserContact and Identities for a domain user

This use case describes how to create UserContact and Identities for a domain user on Active Directory.

Use Case: Create UserContact



Travers CIM_HostedService to CIM_AccountManagementService

Invoke Method CIM_AccountManagementService.CreateUserContact()

Input Parameters

System

Done

UserContactTemplate

UserContactTemplateName: domain\user

Figure 35. Flowchart of Creating UserContact

181


Use Case: Get the UserContact for a specified domain user whose UserContact has been created

This use case describes how to get the UserContact for a specified domain user whose UserContact has been created in the system.

Use Case: Get UserContact for a Specified Domain User



Travers CIM_HostedService to CIM_AccountManagementService

Invoke Method CIM_AccountManagementService.getUserContact()

Input Parameters

Done

UserID

UserIDFormat: domain\user

Figure 36. Flowchart of Getting UserContact

182


Use Case: Removal of an existing UserContact

Client can invoke intrinsic method DeleteInstance on CIM_UserContact to remove the target instance of UserContact.

Use Case: Get the Privilege and UserContact by an Exported File Share

This use case describes how to get the Privilege and UserContact by an Exported FileShare.

Use Case: Get Privilege and UserContat by an Exported Share

Reference CIM_AssociatedPrivilege(Target)

Done

CIM_FileShare

Get Property CIM_AssociatedPrivilege.Activities

Get Property CIM_AssociatedPrivilege.Subjcet

Traverse CIM_AssignedIdentity to CIM_UserContact

Property Activities represents the privilege assigned to the Identity

Property Subject represents the Identity

Figure 37. Flowchart of Getting Privilege and UserContact by an Exported File Share

183


Use Case: Assign a privilege to a pair of UserContact and Exported File Share

This use case describes how to assign Privilege to a pair of UserContact and Exported FileShare.

Use Case: Assign Privilege to a pair of UserContact and Exported File Share

Invoke Method CIM_FileExportService.AssignPrivilegeToExportedShare()

Input Parameters

FileShareOther parametersActivities

Done

Identities

CIM_UserContactCIM_FileShare

Travers CIM_ServiceAffectsElement to CIM_FileExportService

Travers CIM_AssignedIdenty to CIM_Identity

Figure 38. Flowchart of Assigning Privilege to Exported File Share

Use Case: Modify privilege to a pair of UserContact and Exported File Share

Client can invoke intrinsic method ModifyInstance on CIM_AssociatedPrivilege (associates the File Share and the Identity of the UserContact) to change the granted activities.

Use Case: Removal of the existing privilege

Client can invoke intrinsic method DeleteInstance on CIM_AssociatedPrivilege to remove the target instance of AssociatedPrivilege.

CIM Element

The implemented classes and associations related to the Simple Identity Management Profile in VNX File Storage System can be described as follows:

Table 259. CIM Elements for Simple Identity Management Profile


CIM_AccountManagementService

Celerra_AccountManagementService

Provides methods for UserContact management.

CIM_AssignedIdentity Celerra_AssignedIdentity_UC Associates the UserContact with the

184


_IDY Identity.

CIM _AssociatedPrivilege Celerra_AssociatedPrivilege_CIFSS_IDY

Associates the Identity with the CIFS File Share and provides the privilege (activities) granted to the Identity on the Share.

CIM _HostedService Celerra_HostedService_CCS_AMS

Associates the Account Management Service with its scoping system (NAS Head).

CIM _Identity Celerra_Identity Identity to identify a domain user in Active Directory.

CIM _ServiceAffectsElement Celerra_ServiceAffectsElement_AMS_IDY

Associates the Identity with the Account Management Service.

CIM _UserContact Celerra_UserContact UserContact for a domain user in Active Directory.

Celerra_AccountManagementService

Table 260. Referenced Properties/Methods for Celerra_AccountManagementService





Name Name of the instance.

CreateUserContact() Method for creating UserContact and Identities.

GetUsetContact() Method for getting UserContact.

Celerra_UserContact

Table 261. Referenced Properties/Methods for Celerra_UserContact



Name Label by which the object is known.

UserID User ID of a domain user.

Celerra_Identity

Table 262. Referenced Properties/Methods for Celerra_Identity

185




ElementName SID of a domain user.

Celerra_HostedService_CCS_AMS

Table 263. Referenced Properties/Methods for Celerra_HostedService_CCS_AMS



Dependent Reference of Celerra_AccountManagementService

Celerra_ServiceAffectsElement_AMS_IDY

Table 264. Referenced Properties/Methods for Celerra_ServiceAffecftsElement_AMS_IDY


AffectedElement Reference of Celerra_Identity

AffectingElement Reference of Celerra_AccountManagementService

Celerra_AssignedIdentity_UC_IDY

Table 265. Referenced Properties/Methods for Celerra_AssignedIdentity_UC_IDY


IdentityInfo Reference of Celerra_Identity

ManagedElement Reference of Celerra_UserContact

Celerra_AssociatedPrivilege_CIFSS_IDY

Table 266. Referenced Properties/Methods for Celerra_AssociatedPrivilege_CIFSS_IDY


Subject Reference of Celerra_Identity

Target Reference of Celerra_CIFSShare

PrivilegeGranted Indicates whether the Privilege is granted or denied.

Activities Activities granted or denied.

186


Configurations and Limitations

The limitations of SMI-S API on Control Station can be listed as follows:

Only uxfs file systems will be visible and/or managed via SMI-S interface.

SMI-S provider will not show hidden file systems. Hence SMI-S interface cannot be used to manage such file systems.

Root FileSystems will be kept internal and will not be visible and/or manageable using the SMI-S interface.

File systems can only be created using pools.

Manual Volume Management will not be supported.

For NFS shares, support for setting ‘read-only hosts’, ‘read-write hosts’ and ‘mount access hosts’ is not available.

For CIFS shares, support for read-only, read-write access as well as settings for passwords for read-only and read-write access is not available.

For CIFS shares, the maximum number of users cannot be set using SMI-S interface.

You cannot modify the CIFS Share name using SMI-S interface.

Control Stations and standby relationship between two Control Stations will not be visible through SMI-S interface.

Certain attributes in Component object is not populated by backend component. Whenever there is no value for any such attribute from backend component, SMI-S interface will put in _ (an underscore) as the default value.

Pre-defined support of indication filter is not available to SMI-S interface. There is no support from ECOM either.

Most of the indications need to be sent only if there is OperationalStatus change for a particular object. Since backend component does not provide the previous copy of the object, it is not possible for the SMI-S interface to determine whether OperationalStatus of the object has changed or not. To overcome this limitation, SMI-S interface will forward all indications from backend component assuming that OperationalStatus has changed.

A CIFS Share can only be created with only one CIFS server that works in the same way as the FileExportService’s CIFS server does.

EMC VNX Series · PDF filePrivilege Assignment ... 134 Use Case: Well ... Celerra_SystemPackaging_CSC_PCSCS

Documents