Dell™ PowerVault™ ML6000 SMI-S Reference Guide www.dell.com | support.dell.
Information in this document is subject to change without notice. © 2005 - 2010 Dell Inc. All rights reserved. Trademarks used in this text: Dell, the DELL logo, and PowerVault are trademarks of Dell Inc. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.
Contents 1 About This Guide and Your Product 1 Explanation of Symbols and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Other Documents you Might Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Getting More Information or Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A MOF Files 17 MOF File for the PowerVault ML6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 B References 35 Web Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 CIM-XML Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Guide and Your Product This reference guide provides a high-level overview of Storage Management Initiative-Specification (SMI-S) and the Common Information Model (CIM) for use with the PowerVault™ ML6000 libraries. It describes how to use CIM and Managed Object Format (MOF) files to obtain physical and logical entity information from your library, and how to use CIM indications to monitor the status of the library.
Other Documents you Might Need The following documents are also available for this product. These documents can be found on the product CD. • Dell PowerVault ML6000 Tape Library User’s Guide Getting More Information or Help More information about this product is available at http://support.dell.com.
Understanding SMI-S, CIM, and MOF The ML6000 library supports the industry standard SMI-S application programming interface (API) described in the Storage Management Initiative Specification (SMI-S) version 1.2. SMI-S is a standard management interface that facilitates the management of multi-vendor devices in a storage area networks (SANs) environment.
Your Library, SMI-S, and CIM A CIM server is embedded within the ML6000 library. The CIM server is SMI-S compliant and contains a Server profile and several subprofiles. For details about these profiles, refer to CIM Profiles and Subprofiles on page 7. Understanding CIM CIM is an object-oriented information model that describes management information in a network or enterprise environment.
After you have defined the NetworkDevice class, you can define a class for just switches. Since a switch is a special type of NetworkDevice, you can use the object-oriented concept of inheritance to define your Switch class. You can define the Switch class as a child of the NetworkDevice class, meaning that the Switch class automatically has the properties and methods of its parent class. From there, you can add properties and methods unique to a switch.
6 Understanding SMI-S, CIM, and MOF
CIM Profiles and Subprofiles SMI-S defines a number of profiles that specify the managed objects that control and monitor elements of a Storage Area Network (SAN). The CIM server embedded within your library supports the following standard profiles: • Server Profile, Version 1.2 • Storage Library Profile, Version 1.2 When using CIM servers to manage a network of SAN elements, you must first discover the location of all available CIM servers and discover which services they support.
Figure 1 8 Storage Library Profile, Version 1.
Storage Library Subprofiles The following subprofiles are available for the storage library profile. Library Capacity Subprofile Using the ConfigurationCapacity and ElementCapacity classes, servers publish the minimum and maximum number of slots, drives, magazines, media changers, and other elements associated with the library. Software Subprofile Using the SoftwareIdentity class, provides information on the installed controller software.
Element Counting Subprofile The Element Counting Subprofile defines methods to count the number of physical tapes, storage media locations, and other classes within a storage library (or other system type). Such methods allow clients to avoid retrieving all instances of physical element classes simply to count them. Therefore, network traffic will be saved between client applications and storage library providers.
Service Discovery and CIM Indications This chapter explains how to discover the CIM server embedded within your library, and how to use CIM indications to help you monitor the status of the library. Setting up Authentication and Privacy To use the CIM server embedded within your library, the CIM server must be enabled and your CIM clients must connect to it using the appropriate credentials. Enabling the CIM Server The CIM server uses port 5988 for HTTP and port 5989 for HTTPS.
Discovering the CIM Server When you discover the CIM server that is embedded within your library, you not only determine its location within your SAN, but you also determine which services it supports (as defined by the server’s profiles). Discovering CIM servers provides information about the physical and logical entities within your SAN. This information changes dynamically as SAN entities are added, moved, or removed.
Table 1 CIM Methods Method How it is Used enumerateInstances() Enumerates instances of a CIM class enumerateInstanceNames() Enumerates names of instances of a CIM class getInstance() Gets a CIM instance associators() Enumerates associators of a CIM object associatorName() Enumerates names of associators of a CIM object references() Enumerates references to a CIM object referenceName() Enumerates names of references to a CIM object Using CIM Indications A CIM indication is a message that co
Table 2 Supported Queries for CIM Indications Area of Library Library Robotics I/E Station and Tape Media Tape Drives/ I/O Blades 14 Query Purpose SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_ComputerSystem Indicates that the library is available for use (after it has been powered on or restarted). SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_ComputerSystem Indicates that the library is shutting down.
Table 2 Area of Library Supported Queries for CIM Indications (Continued) Query Purpose SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_MediaAccessDevice AND PreviousInstance.OperationalStatus <> SourceInstance.OperationalStatus Indicates a change in the library’s RAS status for tape drives. SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_FCPort Indicates that a Fibre Channel tape drive or FC I/O blade has been added to the library.
16 Service Discovery and CIM Indications
MOF Files The Managed Object Format (MOF) files for the PowerVault ML6000 library are reproduced below.
// =================================================================== // Chassis // =================================================================== [Description("CMPI SMIS Chassis provider"), provider("cmpi::cmpichassis") ] class SMIS_Chassis : CIM_Chassis { }; // =================================================================== // Product // =================================================================== [Description("CMPI SMIS Product provider"), provider("cmpi::cmpiproduct") ] class SMIS_Prod
{ }; // =================================================================== // FCPort // =================================================================== [Description("CMPI SMIS FCPort provider"), provider("cmpi::cmpifcport") ] class SMIS_FCPort : CIM_FCPort { [Description ("Generate indication")] uint32 GenerateIndication(); }; // =================================================================== // SCSIProtocolController // =================================================================== [Descrip
[Description("CMPI SMIS ElementConformsToProfile provider"), provider("cmpi::cmpielementconformstoprofile") ] class SMIS_ElementConformsToProfile : CIM_ElementConformsToProfile { }; // ================================================================== // HostedService // ================================================================== [Description("CMPI SMIS HostedService provider"), provider("cmpi::cmpihostedservice") ] class SMIS_HostedService : CIM_HostedService { }; // ==============================
// ObjectManager // ================================================================== [Description("CMPI SMIS ObjectManager provider"), provider("cmpi::cmpiobjectmanager") ] class SMIS_ObjectManager : CIM_ObjectManager { }; // ================================================================== // ComputerSystemPackage // ================================================================== [Description("CMPI SMIS ComputerSystemPackage provider"), provider("cmpi::cmpicomputersystempackage") ] class SMIS_Comput
// ================================================================== // CommMechanismForManager // ================================================================== [Description("CMPI SMIS CommMechanismForManager provider"), provider("cmpi::cmpicommmechanismformanager") ] class SMIS_CommMechanismForManager : CIM_CommMechanismForManager { }; // ================================================================== // CIMXMLCommunicationMechanism // =============================================================
{ }; // ================================================================== // NamespaceInManager // ================================================================== [Description("CMPI SMIS NamespaceInManager provider"), provider("cmpi::cmpinamespaceinmanager") ] class SMIS_NamespaceInManager : CIM_NamespaceInManager { }; // ================================================================== // Realizes // ================================================================== [Description("CMPI SMIS Realizes
[Description("CMPI SMIS TapeDrive provider"), provider("cmpi::cmpitapedrive") ] class SMIS_TapeDrive : CIM_TapeDrive { [Description ("Generate indication")] uint32 GenerateIndication(); }; // ================================================================== // Magazine // ================================================================== // [Description("CMPI SMIS Magazine provider"), // provider("cmpi::cmpimagazine") // ] //class SMIS_Magazine : CIM_Magazine //{ //}; // ===============================
}; // ================================================================== // PhysicalMediaInLocation // ================================================================== [Description("CMPI SMIS PhysicalMediaInLocation"), provider("cmpi::cmpiphysicalmediainlocation") ] class SMIS_PhysicalMediaInLocation : CIM_PhysicalMediaInLocation { }; // ================================================================== // PhysicalPackage // ================================================================== [Description
] class SMIS_PackageInChassis : CIM_PackageInChassis { }; */ // ================================================================== // ProtocolControllerForUnit // ================================================================== [Description("CMPI SMIS ProtocolControllerForUnit provider"), provider("cmpi::cmpiprotocolcontrollerforunit") ] class SMIS_ProtocolControllerForUnit : CIM_ProtocolControllerForUnit { }; // ================================================================== // ProtocolControllerForP
[Description("CMPI SMIS ElementSoftwareIdentity provider"), provider("cmpi::cmpielementsoftwareidentity") ] class SMIS_ElementSoftwareIdentity : CIM_ElementSoftwareIdentity { }; // ================================================================== // LimitedAccessPort // ================================================================== [Description("CMPI SMIS LimitedAccessPort provider"), provider("cmpi::cmpilimitedaccessport") ] class SMIS_LimitedAccessPort : CIM_LimitedAccessPort { }; // ==============
// RemoteServiceAccessPoint // ================================================================== [Description("CMPI SMIS RemoteServiceAccessPoint provider"), provider("cmpi::cmpiremoteserviceaccesspoint") ] class SMIS_RemoteServiceAccessPoint : CIM_RemoteServiceAccessPoint { }; // ================================================================== // HostedAccessPoint // ================================================================== [Description("CMPI SMIS HostedAccessPoint provider"), provider("cmpi::
// ================================================================== // CommMechanismForManagerAdapter // ================================================================== [Description("CMPI SMIS CommMechanismForManagerAdapter provider"), provider("cmpi::cmpicommmechanismformanageradapter") ] class SMIS_CommMechanismForObjectManagerAdapter : CIM_CommMechanismForObjectManagerAdapter { }; // ================================================================== // SAPAvailableForElement // ====================
class SMIS_PortImplementsEndpoint : CIM_PortImplementsEndpoint { }; // ================================================================== // CIM_DeviceServicesLocation // ================================================================== [Description("CMPI SMIS DeviceServicesLocation provider"), provider("cmpi::cmpideviceserviceslocation") ] class SMIS_DeviceServicesLocation : CIM_DeviceServicesLocation { }; // ================================================================== // ConfigurationReportingS
] class SMIS_AuthorizedPrivilege : CIM_AuthorizedPrivilege { }; // ================================================================== // CIM_AuthorizedSubject // ================================================================== [Description("CMPI SMIS AuthroizedSubject provider"), provider("cmpi::cmpiauthorizedsubject") ] class SMIS_AuthorizedSubject : CIM_AuthorizedSubject { }; // ================================================================== // CIM_AuthorizedTarget // ==========================
// ================================================================== [Description("CMPI SMIS StorageClientsettingData provider"), provider("cmpi::cmpistorageclientsettingdata") ] class SMIS_StorageClientSettingData : CIM_StorageClientSettingData { }; // ================================================================== // CIM_ElementSettingData // ================================================================== [Description("CMPI SMIS ElementSettingData provider"), provider("cmpi::cmpielementsettingda
// =================================================================== // SPIPort // =================================================================== [Description("CMPI SMIS SPIPort provider"), provider("cmpi::cmpispiport") ] class SMIS_SPIPort : CIM_SPIPort { }; Dell PowerVault ML6000 SMI-S Reference Guide 33
34 MOF Files
References This Appendix lists some web resources and popular Common Information Model (CIM)-XML tools. Web Resources Information about the following standards organizations are accessible on the internet: • Website for the Storage Networking Industry Association (SNIA): http://www.snia.org • Website for the Distributed Management Task Force (DMTF): http://www.dmtf.org CIM-XML Tools The following tools are available from these websites: • Open Web Based Enterprise Management (WBEM): http://www.
36 References
SMI-S Common Protocol Interface Specification This section provides a detailed list of the SMI-S feature set that is supported on PowerVault ML6000 libraries and provides updates for the SMI-S1.2.0 and other extensions. Resources Web information about the following standards organizations are accessible on the Internet: • Website for the Storage Networking Industry Association (SNIA): http://www.snia.org • Website for the Distributed Management Task Force (DMTF): http://www.dmtf.
• Limited Access Port subprofile • Software subprofile The following subprofiles are used in modeling; however this version does not claim support of such profiles as they are not supported subprofiles of the SML profile. As of SMI-S 1.3.0, these will be supported by SML and then they will be officially supported by the implementers of this spec.
Requirements General Purpose SMI-S Server Overview The General Purpose SMI-S Server role can provide a hosting environment for the plug-in instrumentation of host-based resources and management proxies for resources with remote management protocols. This plug-ins are called providers and considered sub roles of the General Purpose SMI-S Server. SLP The General Purpose SMI-S Server role MUST implement SLP Service agent (SA) functionality using the required template: www.dmtf.org/standards/wbem/wbem.1.0.
Figure 3 Instance Diagram for Server Profile Table 4 Required Properties for ObjectManager Property Type SystemCreationClassName[key] string, MaxLen(256) SystemName[key] string CreationClassName[key] string Name[key] String, MaxLen(256) ElementName String Description String OperationalStatus Uint16[] StatusDescriptions String[] Started Boolean 40 Description/Notes Host name of the library MUST NOT be NULL if Other is identified in OperationalStatus SMI-S Common Protocol Interface
Table 5 Required Server Level Instances of ObjectManager Property Instance 1 SystemCreationClassName[key] “CIM_ComputerSystem” SystemName[key] CreationClassName[key] “CIM_ObjectManager” Name[key] “owcimomd” ElementName “CIM_ObjectManager” Description “owcimomd” OperationalStatus Example : OK(2) StatusDescriptions OK Started TRUE Table 6 Required Properties for HostedService Property Type Description/Notes Antecedent REF The hosting system Dependent R
Table 8 Required Properties for RegisteredProfile Property Type Description/Notes InstanceID[key] String This is a unique value for the profile instance. RegisteredOrganization String, MAXLEN(256) Required This is the official name of the organization that created the Profile. For SMI-S profiles, this would be SNIA. OtherRegisteredOrganization String, MAXLEN(256) RegisteredName String, MAXLEN(256) Required This is the name assigned by the organization that created the profile.
Table 10 Required Properties for RegisteredSubProfile Property Type Description/Notes InstanceID[key] String This is a unique value for the profile instance. RegisteredOrganization String, MAXLEN(256) Required This is the official name of the organization that created the Profile. For SMI-S profiles, this would be SNIA. OtherRegisteredOrganization String, MAXLEN(256) RegisteredName String, MAXLEN(256) Required This is the name assigned by the organization that created the profile.
Property Instance 5 Instance 6 Instance 7 Instance 8 InstanceID[key] “SNIA:Storage Library:Storage Library Capacity” “SNIA:Storage Library:FC Target Ports” “SNIA:Storage Library:Elemen t Counting” “SNIA:Server:Indi cation” RegisteredOrganization SNIA(11) SNIA(11) SNIA(11) SNIA(11) RegisteredName “SNIA:Storage Library:Capacity” “SNIA:FC Target Ports” “SNIA:Element Counting” “SNIA:Indication” RegisteredVersion “1.2.0” “1.2.0” “1.2.0” “1.2.
Table 13 Required Server Level Instances of SubProfileRequiresProfile Property Instance 1 Antecedent CIM_RegisteredProfile Dependent CIM_RegisteredSubProfile Table 14 Required Properties for ElementConformsToProfile Property Type Description/Notes ConformantStandard REF The RegisteredProfile to which the ManagedElement conforms. ManagedElement REF The ManagedElement that conforms to the RegisteredProfile.
Table 17 Required Server Level Instances of Namespace Property Instance 1 SystemCreationClassName[key] “CIM_System” SystemName[key] ObjectManagerCreationClassName “CIM_ObjectManager” ObjectManagerName “owcimomd” CreationClassName “CIM_Namespace” Name “root/cimv2” ClassInfo CIM 2.9 (11) Table 18 Required Properties for NamespaceInManager Property Type Description/Notes Antecedent REF The ObjectManager containing a Namespace.
Table 20 Required Properties for CIMXMLCommunicationMechanism Property Type ElementName String CreationClassName[key] String, MaxLen(256) SystemCreationClassName[key] String, MaxLen(256) SystemName[key] String Name[key] String, MaxLen(256) OperationalStatus Uint16[ StatusDescriptions String[] MUST NOT be NULL if “Other” is identified in OperationalStatus.
Table 21 Required Server Level Instances for CIMXMLCommunicationMechanism Property Instance 1 ElementName “CIM_CIMXMLCommunicationMechanism” CreationClassName[key] “CIM_CIMXMLCommunicationMechanism” SystemCreationClassName[key] “CIM_ObjectManager” SystemName[key] Name[key] “CIM_CIMXMLCommunicationMechanism” OperationalStatus OK(2) StatusDescriptions “OK” CommunicationMechanism CIM-XML (2) OtherCommunicationMechanismDescription FunctionalProfilesSupported { Bas
Table 24 Required Properties for ComputerSystem Property Type Description/Notes CreationClassName[key] String Name of Class Name[key] String For component computer systems, the provider MUST provide a unique name using one of the NameFormats. Dedicated Uint16[] Container type (for example, SML). OperationalStatus Uint16[] Container status. ElementName String User-friendly name.
Storage Library Profile Content Figure 4 ComputerSystem-Centric Instance Diagram of StorageLibrary Profile ConfigurationCapacity Product ProductPhysicalComponent Location Chassis ElementCapacity PhysicalElementLocation PackageInChassis ComputerSystemPackage PhysicalPackage (Drive) PackagedCompon ComputerSystem SystemDevice ProtocolControllerForPort SPIPort SASPort Physical Tape Physical Tape FCPort Containe PortImplementsEndpoint Realizes PortImplementsEndpoint System Device SCSIProtocolC
Table 26 Required Container Level Instances of ComputerSystem Property Instance 1 CreationClassName[key] “CIM_ComputerSystem” Name[key] Vendor + Product + Serial Example: DELL ML6000 SNA12345678 Dedicated sml (22) OperationalStatus Example : ok(2) ElementName “CIM_ComputerSystem” NameFormat ”HID” Automated True PrimaryOwnerName Owner Name from contact info PrimaryOwnerContact Owner Phone + Owner E-mail from contact info Caption ComputerSystem Description Tape Library Backup Unit Ta
Table 28 Required Container Level Instances of Chassis Property Instance (one per module) Tag[key] Module (CM/EM) location number (0, -1, 1, etc.). CreationClassName[key] “CIM_Chassis” Serial Number Module serial number Model ”ControlModuleFrame” or “ExpansionModuleXU” module where XU is the module size Manufacturer "DELL" LockPresent False SecurityBreach Breach Successful if any door open or No Breach(3) if all doors closed.
Table 32 Required Server Level Instances of PhysicalElementLocation Property Instance 1 Element CIM_Chassis PhysicalLocation CIM_Location Figure 5 Instance Diagram of ComputerSystemPackage IdentifyingNumber is the library serial number SerialNumber is the module serial number, not the library serial number. Note: The Dell PowerVault ML6000 is modeled to have a chassis for each module.
Table 35 Required Properties for Product Property Type Description/Notes Name[key] String, MaxLen(256) Commonly used product name. IdentifyingNumber[key] String, MaxLen(64) Product identification such as a serial number on software, a die number on a hardware chip, or a project number. Vendor[key] String, MaxLen(256) The name of the product supplier, or entity selling the product. Version[key] String, MaxLen(64) Firmware version information. ElementName String User-friendly name.
Table 39 Required Properties for SoftwareIdentity Property Type Description/Notes InstanceID[key] String Instance name. VersionString String Version. Manufacturer String Manufacturer of this software.
Table 42 Required Server Level Instances of InstalledSoftwareIdentity Property Library System Instance Drive Instances System CIM_ComputerSystem for Library (HID) CIM_TapeDrive for drive. InstalledSoftware CIM_SoftwareIdentity “PowerVault ML6000" CIM_SoftwareIdentity for corresponding drive software instance. Server Instance (one for System) Changer Instances (one for each changer) System CIM_ComputerSystem for Server CIM_ChangerDevice.
Table 46 Required Container Level Instances of ConfigurationCapacity Property Instance 1 Instance 2 Instance 3 Name[key] “Tape Library Maximum Slots” “Tape Library Number of Tapes” “Tape Library Number of Tape Drives” ObjectType[key] StorageMediaLocation Slots ( 8 ) Other (0) MediaAccessDevices ( Drives ) (7) MaximumCapacity Depends on library configuration Same as instance 1 Depends on library configuration OtherTypeDescription “Estimated number of maximum slots” “Estimated number of ma
Table 48 Required Library Level Instances of SystemDevice Property FCPort Instances (one for each FC Port) SASPort Instances (one for each SAS Port) SPI Port Instances (one for each FC Port) GroupComponent CIM_ComputerSystem* CIM_ComputerSystem CIM_ComputerSystem PartComponent CIM_FCPort CIM_SASPort CIM_SPIPort * For FCPort, SCSIProtocolEndpoint and SCSIProtocolController, they may have a SystemDevice association to the ComputerSystem of the blade, not the library (for example, if the object r
Table 51 Property Required Library Level instances of Realizes Accessor Instances (one for each partition + physical) Drive Instances (one for each drive) IE Instances (one for each IE slot) Antecedent CIM_StorageM ediaLocation CIM_StorageMediaLocation CIM_StorageMediaLocation Dependent CIM_Changer Device CIM_TapeDrive CIM_LimitedAccessPort Property Changer Package (one for system) Drive Package Instances (one for each drive) Chassis IE (one for each IE slot) Antecedent CIM_PhysicalP ackag
Table 52 Required Properties for FCPort Property Type SystemCreationClassName[key] String SystemName[key] String CreationClassName[key] String DeviceID[key] String PortNumber Uint16 PermanentAddress String ElementName String OperationalStatus Uint16 Port Status. NetworkAddress String FCID. PortType Uint16 Port Type. ActiveFC4Types Uint16 Supported FC types. OtherNetworkPortType String Describes the type of module, when PortType is set to 1 ("Other").
Table 53 Required Direct Attached Drive Front-End Ports Instances of FCPort Property Description/Notes SystemCreationClassName[key] “CIM_ComputerSystem” SystemName[key] CreationClassName[key] “CIM_FCPort” DeviceID[key] “D::::" PortNumber Example: 1 PermanentAddress WW Port Name Format is 16 octets 1234567887654321 ElementName “FC Port” OperationalStatus Example : ok(2) NetworkAddress 0 PortType Example: N(10
Table 55 Required Library Level Instances of SASPort Property Value (one for each SAS drive) SystemCreationClassName[key] CIM_ComputerSystem SystemName[key] CreationClassName[key] CIM_SCSIProtocolController DeviceID[key] PermanentAddress SAS UID Description “SCSI port on drive ” OperationalStatus Status of drive Caption Table 56 Required Properties for SPIPort Property Type SystemCreationClassName[key] String SystemName[key] St
Table 57 Required Library Level Instances of SPIPort Property Value SystemCreationClassName[key] CIM_ComputerSystem SystemName[key] CreationClassName[key] CIM_SPIPort DeviceID[key] PermanentAddress “” NetworkAddresses {} Description “SCSI port on drive " OperationalStatus Status of drive MaxDataWidth Maximum bus width MaxTransferRate Maximum data transfer rate Caption Table 58 Required Properties for ChangerDevice
Table 59 Required Server Level Instances of ChangerDevice Property Physical Library Instance 1 Partition Instances (one for each partition) SystemCreationClassName[key] “CIM_ComputerSystem” “CIM_ComputerSystem” SystemName[key] CreationClassName[key] “CIM_Computersystem” “CIM_Computersystem” DeviceID[key] “::” “::” MediaFlipSupported False False ElementName “SMIS_ChangerDevice” “SMIS_ChangerDevice”
Table 62 Required Properties for SCSIProtocolController Property Type Description/Notes SystemCreationClassName[key] string, MaxLen(256) The scoping System's CreationClassName. SystemName[key] string The scoping System's Name. CreationClassName[key] string Indicates the name of the class or subclass used in the creation of an instance.
Table 63 Required Server Level Instances of SCSIProtocolController Property Drive Instances (one for each direct-attached drive) SystemCreationClassName[key] “CIM_ SCSIProtocolController” SystemName[key] IP CreationClassName[key] “CIM_ComputerSystem” DeviceID[key] ”D::: :” MaxUnitsControlled 2048 ElementName “SMIS_SCSIProtocolController” OperationalStatus[valuemap] {Unknown(0)} Caption Same as DeviceID Description “Tape Drive ” where
Table 65 Required Library Instances of SCSIProtocolEndpoint Property Drive Instances (one for each direct-attached drive) SystemCreationClassName[key] “CIM_ComputerSystem” SystemName[key] HID CreationClassName[key] “CIM_SCSIProtocolEndpoint” DeviceID[key] ”” ConnectionType Fibre Channel (2) Role Target (3) OperationalStatus[valuemap] {Unknown(0)} ProtocollFType Fibre Channel (56) Description “SMIS_SCSIProtocolEndpoint” Table 66 Required Properties of PortImplementsEndpoint Prop
Table 69 Required Library Instances of SAPAvailableForElement Property Instance (one for each SCSIProtocolController) AvailableSAP CIM_SCSIProtocolEndpoint ManagedElement CIM_SCSIProtocolController Table 70 Required Properties for ElementSoftwareIdentity Property Type Description/Notes Antecedent REF The SoftwareIdentity. Dependdent REF The ManagedElement that requires or uses the software.
Table 72 Required Properties for TapeDrive Property Type Description/Notes SystemCreationClassName[key] string, MaxLen(256) The scoping System's CreationClassName. SystemName[key] string The scoping System's Name. CreationClassName[key] string Indicates the name of the class or subclass used in the creation of an instance. DeviceID[key] string , MaxLen(256) Opaque Availability Uint16 NeedsCleaning Boolean Boolean indicating that the MediaAccessDevice needs cleaning.
Table 73 Required Server Level Instances of TapeDrive Property Type SystemCreationClassName[key] “CIM_TapeDrive” SystemName[key] CreationClassName[key] “CIM_ComputerSystem” DeviceID[key] ”:: ” Availability Running/Full Power(3) or Offline (8) NeedsCleaning False PowerOnHours Hours since last drive power TotalPowerOnHours Total hours the drive has been on OperationalStatus [valuemap] {OK(2)} MountCount Number of times the drive has been mounted Tabl
Table 77 Required Library Level Instances of PhysicalPackage Property Tape Drive Instances (one for each drive) Control Module Instances (one for the system) CreationClassName[key] “CIM_PhysicalPackage” “CIM_PhysicalPackage” Tag[key] ”:” “:” Manufacturer Vendor (example: “IBM”) Branding Model Product ID (example: “ULTRIUM-TD3”) “ControlModule5U” Caption Same as Tag Serial Number Table 78 Required Propertie
Table 79 Required Server Level Instances of PhysicalTape Property Instance (one for each present cartridge) Tag[key] ”::0” CreationClassName[key] “SMIS_PhysicalTape” Capacity Size of data on tape12345 MediaType LTO Ultrium(7) MediaDescription “LTO 1” CleanerMedia Boolean DualSided False PhysicalLabels Barcode {“12345”}] EncryptionState 0 Unknown, 1 Unencrypted, 2 Encrypted Table 80 Required Properties for PackagedComponent Property Type Description/Notes G
Table 83 Required Server Level Instances of StorageMediaLocation Property Type Tag[key] ..
Table 88 Required Properties of LimitedAccessPort Property Type Description/Notes SystemCreationClassName[key] String, MaxLen(256) The scoping system's CreationClassName. SystemName[key] String The scoping system's name. CreationClassName[key] String Indicates the name of the class or subclass used in the creation of an instance. DeviceID[key] String, MaxLen(256) Opaque.
Table 92 Creation/Deletion of a TapeDrive Query Comments/Remarks SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_TapeDrive SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_TapeDrive Event to notify when a tape drive comes into the library or leaves the library.
Table 97 Change in Operational Status of a TapeDrive Query Comments/Remarks SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_TapeDrive AND PreviousInstance.OperationalStatus <> SourceInstance.OperationalStatus Event to notify change in operational status of a tape drive. Table 98 Change in Operational Status of a ChangerDevice Query Comments/Remarks SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_ChangerDevice AND PreviousInstance.OperationalStatus <> SourceInstance.
Fibre Channel Blade Support This support for Fibre Channel blades is provided through objects belonging to the following SMI-S subprofiles: • The Multiple Computer System Subprofile • The Masking Mapping Profile As of 1.2.0, these subprofiles are not supported by the Storage Media Library profile, and so the Dell PowerVault ML6000 does not show support for them in the Profile Registration Subprofile. The diagram below shows the library object model with blade support.
Table 100 Fibre Channel I/O Blade Instances of Computer System Property Instances (one per Fibre Channel I/O Blade) CreationClassName[key] “CIM_ComputerSystem” Name[key] Blade WWNN Dedicated Router (4) OperationalStatus Blade state, example: ok(2) OtherIdentifyingInfo “ComputerSystem” ElementName “SMIS_FCBComputerSystem” NameFormat "WWN” PrimaryOwnerName "DELL" PrimaryOwnerContact "“ CaptionBlade WWN Description This is a Fibre Channel I/O blade Table 101 Required Properties for C
Table 103 Required Blade Instances of FCPort Property Blade Instances (one for each blade target FC port) SystemCreationClassName[key] “CIM_ComputerSystem” SystemName[key] CreationClassName[key] “SMIS_FCPort” DeviceID[key] "B::::WWN” PortNumber Example: 1 PermanentAddress WW Port Name Format is 16 octets 1234567887654321 ElementName "CIM_FCPort” OperationalStatus Port Status.
Table 105 Required Blade Instances of SCSIProtocolEndpoint Property Drive Instances (one for each direct-attached drive) SystemCreationClassName[key] “CIM_ComputerSystem” SystemName[key] HID CreationClassName[key] “CIM_SCSIProtocolEndpoint” DeviceID[key] ”” ConnectionType Fibre Channel (2) Role Target (3) OperationalStatus [valuemap] {Unknown(0)} ProtocolIFType Fibre Channel (56) Description “SMIS_SCSIProtocolEndpoint” Table 106 Required Blade Instances of PortImplementsEndpoint
Table 109 Required Blade Instances of SystemDevice Property FCPort Instances (one for each target port) SPC Instances (one for each SPC) SPE Instances (one for each target port) GroupComponent CIM_ComputerSystem CIM_ComputerSystem CIM_ComputerSystem PartComponent CIM_FCPort CIM_SCSIProtocolController CIM_SCSIProtocolEndpoint Table 110 Required Blade Instances of InstalledSoftwareIdentity Property Instance 1 (one for each Fibre Channel I/O blade) System CIM_ComputerSystem InstalledSoftwar
LUN Mapping (EVPS) The implementation of LUN Mapping is done for blade systems and is applicable for when the LUN Mapping (EVPS) feature is enabled on the library. The implementation is done using the objects of the SMI-S 1.2.0 Mapping and Masking Subprofile, but the library does not claim support for it because the SML Profile does not support it as of 1.2.0. The diagram below shows the object model with LUN mapping.
Table 113 Required Properties for StorageHardwareID Property Type Description/Notes InstanceID[key] String This is a unique value for the instance CurrentlyAuthenticated Boolean Whether the identity has been authenticated (optional) StorageID String The hardware ID IDType Uint16 Type of ID PortWWN, iSCSI, etc.
Table 117 Required Properties for AuthorizedPrivilege Property Type Description/Notes InstanceID[key] String This is a unique value for the instance PrivilegeGranted Boolean Whether privilege has been granted or denied (optional) Activities [valuemap] Uint16 array Read/write/create… Table 118 Required Instances for AuthorizedPrivilege Property Instance (one for each host-blade combination) InstanceID[key] ::: PrivilegeGranted T
Table 123 Required Properties for AuthorizedTarget Property Type Description/Notes Privilege REF Privilege grant or denial TargetElement REF The object to be accessed Table 124 Required Instances for AuthorizedTarget Property Value (one for each blade-host-port combination) Privilege CIM_AuthorizedPrivilege of the blade-initiator combination TargetElement CIM_SCSIProtocolController for blade-host-port combination Table 125 Required Properties for ProtocolControllerMaskingCapabilities Pr
Table 126 Required Instances for ProtocolControllerMaskingCapabilities Top-level ComputerS ystem Blade LUN Mapping On Blade LUN Mapping Off InstanceID[key] :“L” :”E” :”B” ElementName “CS SPC Masking Capabilities” “EVPS Enabled SPC Masking Capabilities” “EVPS Disabled SPC Masking Capabilities” ValidHardwareIDTypes {2} (wwpn) {2} (wwpn) {2} (wwpn) PortsPerView 1 1 Multiple ClientSelectableDeviceNumbers False True False OneHard
Table 128 Required Instances for ElementCapabilities Property Instance (one for each computer system) Capabilities CIM_ProtocolControllerMaskingCapabilities ManagedElement CIM_ComputerSystem Table 129 Lun Mapping Instances of SCSIProtocolController When LUN mapping is enabled, there is a an instance for each host-blade-port combination.
88 SMI-S Common Protocol Interface Specification
Index C CIM about . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 CIM-XML . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 indications . . . . . . . . . . . . . . . . . . . . . . . . . . 13 methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 profiles and subprofiles . . . . . . . . . . . . . . . . . 7 server . . . . . . . . . . . . .
90 Index
