ISO/IEC 24775-8:2021

INTERNATIONAL ISO/IEC
STANDARD 24775-8
Second edition
2021-03
Information technology — Storage
management —
Part 8:
Media libraries
Reference number
©
ISO/IEC 2021
© ISO/IEC 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2021 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical activity.
ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of document should be noted (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details
of any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC list of patent
declarations received (see http://patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the World
Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT),
see www.iso.org/iso/foreword.html.
This document was prepared by SNIA (as Storage Management Technical Specification, Part 7 Host
Elements, Version 1.8.0, Revision 5) and drafted in accordance with its editorial rules. It was adopted,
under the JTC 1 PAS procedure, by Joint Technical Committee ISO/IEC JTC 1, Information technology.
This second edition cancels and replaces the first edition (ISO/IEC 24775-7:2014), which has been
technically revised.
The main changes compared to the previous edition are as follows:
— USAGE text was revised to address code (now included in the front matter for all SNIA specifications)
— All recipes and their references were deleted.
— Instances of subprofile were changed to profile. In the annex, instances of subprofile were changed
to component profile (TSG meeting voice vote).
— Profile versions and related text were updated. (TSG meeting voice vote).
— Indications have been replaced by DMTF Indications, and all affected clauses updated. (TSG meeting
voice vote).
— Instances of Experimental within profiles already labeled as Experimental were removed to avoid
confusion and redundancy. (Editorial change)
— CIM/XML was changed to CIM-XML (Response to ballot comments).
© ISO/IEC 2021 – All rights reserved iii

— Annex: SMI-S Information Model.
— The CIM schema version was changed to 2.51 for V1.8.0 Rev3.
— Disk Partition Profile
— Added descriptions of the references in CIM_BasedOn (Partition to Extent), CIM_BasedOn
(Partition to Partition), CIM_LogicalDiskBasedOnPartition (LogicalDisk to Partition) and
CIM_SystemDevice (System to LogicalDisk).
— Made CIM_LogicalDiskBasedOnPartition (LogicalDisk to Partition) and CIM_SystemDevice
(System to LogicalDisk) Conditional (rather than Optional), since CIM_LogicalDisk is Optional.
Storage HBA Profile (SMI TWG Reviews).
— Fixed the version numbers on the Related Profiles to match what the profiles claim.
— Added Descriptions to the references in CIM_ProductElementComponent, CIM_Realizes and
CIM_SystemDevice.
— FC HBA Profile
— Removed the profile content and added text re it being Deprecated. (CORE-SMIS-SCR-000).
— Host Discovered Resources Profile
— Promoted the maturity level from DRAFT to EXPERIMENTAL for update to remove SNIA_
classes and use DMTF CIM_ classes.
— Added the related profiles table to the spec.
— Moved NameFormat from LogicalDevice to LogicalDisk to match the mof.
— Moved NameNamespace from LogicalDevice to LogicalDisk to match the mof.
— Added descriptions on the References for CIM_HostedAccessPoint and CIM_SystemDevice.
— Marked the SB Multipath Management Related Profile as Deprecated (SMIS-180-Errata-
SCR00002).
— Host Hardware RAID Controller Profile
— Fixed the version numbers on the Related Profiles to match what the profiles claim.
— Added two ElementSoftwareIdentity associations to cover the 3 SoftwareIdentity classes (one
Mandatory and one Optional).
— Added descriptions on the References for CIM_AssociatedAlarm,
CIM_ProductPhysicalComponent,
CIM_ProtocolControllerForUnit (Extent or MediaAccessDevice), CIM_Realizes (Associates
PhysicalPackage to PortController) and CIM_SAPAvailableForElement.
— Fixed the description of Dependent in CIM_ControlledBy.
— Added Key properties to the CIM_SoftwareIdentity CIM Element tables.
— Changed the version of the profile to 1.7.0.
— iSCSI Initiator
— Removed all occurrences of “(Host Hardware RAID Controller)” (CORE-SMIS-SCR-000).
— Removed MATURITY="Draft" from the Launch In Context supported profile.
— Added Descriptions for References in 2 CIM_BindsTo associations, CIM_ControlledBy, 2
CIM_DeviceSAPImplementations and CIM_ElementSoftwareIdentity.
— Added Descriptions for References in 2 CIM_EndpointOfNetworkPipes,
CIM_NetworkPipeComposition, CIM_ProductPhysicalComponent and CIM_Realizes.
iv © ISO/IEC 2021 – All rights reserved

— Added Descriptions for references in CIM_SAPAvailableForElement.
— Added Keys to CIM_PhysicalPackage.
— Changed the Central Class from PortController to CIM_ComputerSystem (TSG-SMIS-
SCR00333).
— Memory Configuration Profile
— Updated due to class and property name changes in DMTF Multi-type Memory profile (SMIS-
170-Draft-SCR00006).
— Introduced staged request concept.
— Added use cases.
— Addressed comments from internal and partner reviews.
— Changed diagrams approved in Core TWG 3/23/15.
— Changed SystemCreateClassName in class CIM_MemoryConfigurationService to
SystemCreationClassName.
— Changed RemainingCapacity in class CIM_ResourcePool to CurrentlyConsumedResource.
— Changed ChangeableType in class CIM_MemoryAllocationSettingData to ResourceType.
— Fixed the description of Replication in class CIM_MemoryAllocationSettingData.
— Added a description for ChannelCount in class CIM_MemoryAllocationSettingData.
— Persistent Memory Configuration Profile
— Added new material (most of profile content) to manage NVDIMMs (SMIS-170-Draft-
SCR00006).
— Changed diagrams approved in Core TWG 3/23/15- Changed RemainingCapacity in class
CIM_ResourcePool to Reserved.
— Changed SecurityFeatues in class CIM_PersistentMemoryCapabilities to SecurityFeatures.
— Removed ChannelCount in class CIM_PersistentMemoryNamespaceSettingData, since it is not
in the mof and not referenced anywhere in the profile text.
— Added three methods to CIM_PersistentMemoryService to support the profile text.
— Fixed the ManagedElement reference in CIM_ElementConformsToProfile.
— Fixed the references in CIM_SystemDevice.
— Fixed the references in CIM_BasedOn.
— SB Multipath Management Profile
— Promoted the maturity level from DRAFT to EXPERIMENTAL for update to remove SNIA_
classes and use DMTF CIM_ classes (TSG-SMIS-SCR00315.001).
— Added reference to SMI-S Version 1.6.1 Revision 5. No content in this deprecated profile SB
Multipath.
— SCSI Multipath Management Profile
— Added keys to CIM_SCSIMultipathConfigurationCapabilities and CIM_SCSIMultipathSettings
(SMIS-170-Draft-SCR00006).
— Annex A (informative) SMI-S Information Model
— DMTF’s CIM schema version changed to 2.45.0.
— References
© ISO/IEC 2021 – All rights reserved v

— Added DMTF DSP1054 v1.2.2, Indications Profile (and changed version to 1.2.2 throughout
book).
— Updated DSP 1071, Multi-type System Memory Profile reference here and in profiles.
— Added reference to DSP 1119, 1.0.0b Diagnostics Job Control Profile.
— Removed reference to DSP 1119\.
— Removed 2.3.
A list of all parts in the ISO/IEC 24775 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
vi © ISO/IEC 2021 – All rights reserved

1 INTENDED AUDIENCE
2 This document is intended for use by individuals and companies engaged in developing, deploying, and
3 promoting interoperable multi-vendor SANs through the Storage Networking Industry Association (SNIA)
4 organization.
5 CHANGES TO THE SPECIFICATION
6 Each publication of this specification is uniquely identified by a three-level identifier, comprised of a
7 version number, a release number and an update number. The current identifier for this specification is
8 version 1.8.0. Future publications of this specification are subject to specific constraints on the scope of
9 change that is permissible from one publication to the next and the degree of interoperability and
10 backward compatibility that should be assumed between products designed to different publications of
this standard. The SNIA has defined three levels of change to a specification:
• Major Revision: A major revision of the specification represents a substantial change to the underlying scope
or architecture of the SMI-S API. A major revision results in an increase in the version number of the version
identifier (e.g., from version 1.x.x to version 2.x.x). There is no assurance of interoperability or backward
compatibility between releases with different version numbers.
• Minor Revision: A minor revision of the specification represents a technical change to existing content or an
adjustment to the scope of the SMI-S API. A minor revision results in an increase in the release number of
the specification’s identifier (e.g., from x.1.x to x.2.x). Minor revisions with the same version number preserve
interoperability and backward compatibility.
• Update: An update to the specification is limited to minor corrections or clarifications of existing specification
content. An update will result in an increase in the third component of the release identifier (e.g., from x.x.1 to
x.x.2). Updates with the same version and minor release levels preserve interoperability and backward
compatibility.
TYPOGRAPHICAL CONVENTIONS
Maturity Level
In addition to informative and normative content, this specification includes guidance about the maturity
of emerging material that has completed a rigorous design review but has limited implementation in
commercial products. This material is clearly delineated as described in the following sections. The
typographical convention is intended to provide a sense of the maturity of the affected material, without
29 altering its normative content. By recognizing the relative maturity of different sections of the standard, an
30 implementer should be able to make more informed decisions about the adoption and deployment of
31 different portions of the standard in a commercial product.
This specification has been structured to convey both the formal requirements and assumptions of the
33 SMI-S API and its emerging implementation and deployment lifecycle. Over time, the intent is that all
34 content in the specification will represent a mature and stable design, be verified by extensive
35 implementation experience, assure consistent support for backward compatibility, and rely solely on
36 content material that has reached a similar level of maturity. Unless explicitly labeled with one of the
subordinate maturity levels defined for this specification, content is assumed to satisfy these
37 requirements and is referred to as “Finalized”. Since much of the evolving specification
38 content in any given release will not have matured to that level, this specification defines three
subordinate levels of implementation maturity that identify important aspects of the content’s increasing
maturity and stability. Each subordinate maturity level is defined by its level of implementation
experience, its stability and its reliance on other emerging standards. Each subordinate maturity level is
identified by a unique typographical tagging convention that clearly distinguishes content at one maturity
model from content at another level.
© ISO/IEC 2021 – All rights reserved

46 Experimental Maturity Level
No material is included in this document unless its initial architecture has been completed and reviewed.
Some content included in this document has complete and reviewed design, but lacks implementation
experience and the maturity gained through implementation experience. This content is included in order
to gain wider review and to gain implementation experience. This material is referred to as
“Experimental”. It is presented here as an aid to implementers who are interested in likely future
developments within the SMI specification. The contents of an Experimental profile may change as
implementation experience is gained. There is a high likelihood that the changed content will be included
in an upcoming revision of the specification. Experimental material can advance to a higher maturity level
as soon as implementations are available. Figure 1 is a sample of the typographical convention for
Experimental content.
EXPERIMENTAL
Experimental content appears here.
EXPERIMENTAL
Figure 1 - Experimental Maturity Level Tag
Implemented Maturity Level
Profiles for which initial implementations have been completed are classified as “Implemented”. This
indicates that at least two different vendors have implemented the profile, including at least one provider
implementation. At this maturity level, the underlying architecture and modeling are stable, and changes
in future revisions will be limited to the correction of deficiencies identified through additional
implementation experience. Should the material become obsolete in the future, it must be deprecated in a
minor revision of the specification prior to its removal from subsequent releases. Figure 2 is a sample of
the typographical convention for Implemented content.
IMPLEMENTED
Implemented content appears here.
IMPLEMENTED
Figure 2 - Implemented Maturity Level Tag
Stable Maturity Level
Once content at the Implemented maturity level has garnered additional implementation experience, it
can be tagged at the Stable maturity level. Material at this maturity level has been implemented by three
different vendors, including both a provider and a client. Should material that has reached this maturity
level become obsolete, it may only be deprecated as part of a minor revision to the specification. Material
at this maturity level that has been deprecated may only be removed from the specification as part of a
major revision. A profile that has reached this maturity level is guaranteed to preserve backward
compatibility from one minor specification revision to the next. As a result, Profiles at or above the Stable
© ISO/IEC 2021 – All rights reserved

76 maturity level shall not rely on any content that is Experimental. Figure 3 is a sample of the typographical
77 convention for Implemented content.
STABLE
Stable content appears here.
STABLE
Figure 3 - Stable Maturity Level Tag
78 Finalized Maturity Level
79 Content that has reached the highest maturity level is referred to as “Finalized.” In addition to satisfying
80 the requirements for the Stable maturity level, content at the Finalized maturity level must solely depend
81 upon or refine material that has also reached the Finalized level. If specification content depends upon
82 material that is not under the control of the SNIA, and therefore not subject to its maturity level
83 definitions, then the external content is evaluated by the SNIA to assure that it has achieved a
84 comparable level of completion, stability, and implementation experience. Should material that has
85 reached this maturity level become obsolete, it may only be deprecated as part of a major revision to the
86 specification. A profile that has reached this maturity level is guaranteed to preserve backward
87 compatibility from one minor specification revision to the next. Over time, it is hoped that all specification
content will attain this maturity level. Accordingly, there is no special typographical convention, as there is
with the other, subordinate maturity levels. Unless content in the specification is marked with one of the
typographical conventions defined for the subordinate maturity levels, it should be assumed to have
reached the Finalized maturity level.
Deprecated Material
Non-Experimental material can be deprecated in a subsequent revision of the specification. Sections
identified as “Deprecated” contain material that is obsolete and not recommended for use in new
development efforts. Existing and new implementations may still use this material, but shall move to the
newer approach as soon as possible. The maturity level of the material being deprecated determines how
long it will continue to appear in the specification. Implemented content shall be retained at least until the
next revision of the specialization, while Stable and Finalized material shall be retained until the next
major revision of the specification. Providers shall implement the deprecated elements as long as it
appears in the specification in order to achieve backward compatibility. Clients may rely on deprecated
elements, but are encouraged to use non-deprecated alternatives when possible.
Deprecated sections are documented with a reference to the last published version to include the
deprecated section as normative material and to the section in the current specification with the
replacement. Figure 4 contains a sample of the typographical convention for deprecated content.
DEPRECATED
Content that has been deprecated appears here.
DEPRECATED
Figure 4 - Deprecated Tag
© ISO/IEC 2021 – All rights reserved

© ISO/IEC 2021 – All rights reserved

Contents
List of Figures . 13
List of Tables . 15
Foreword . 17
1 Scope . 19
2 Normative References. 21
2.1 General . 21
2.2 Approved references. 21
2.3 References under development . 21
3 Terms, Definitions, Symbols, Abbreviations, and Conventions . 23
3.1 General . 23
3.2 Terms and Definitions . 23
4 Storage Library Profile. 25
4.1 Synopsis. 25
4.2 Description . 25
4.3 Health and Fault Management Considerations. 40
4.4 Methods of the Profile . 40
4.5 Use Cases. 40
4.6 CIM Elements. 42
5 Storage Library Element Counting Profile . 57
5.1 Synopsis. 57
5.2 Description . 57
5.3 Discovery . 57
5.4 Health and Fault Management Considerations. 57
5.5 Methods of the Profile . 57
5.6 Use Cases. 59
5.7 CIM Elements. 61
6 Storage Library Capacity Profile. 63
6.1 Synopsis. 63
6.2 Description . 63
6.3 Health and Fault Management Considerations. 63
6.4 Methods of the Profile . 63
6.5 Use Cases. 64
6.6 CIM Elements. 64
7 Storage Library Limited Access Port Elements Profile . 67
7.1 Synopsis. 67
7.2 Description . 67
7.3 Instance Diagram . 67
7.4 Health and Fault Management Considerations. 68
7.5 Methods of the Profile . 68
7.6 Use Cases. 68
7.7 CIM Elements. 68
Annex A (informative) SMI-S Information Model. 73
© ISO/IEC 2021 – All rights reserved

© ISO/IEC 2021 – All rights reserved

LIST OF FIGURES
Figure 1 - Experimental Maturity Level Tag . 8
Figure 2 - Implemented Maturity Level Tag . 8
Figure 3 - Stable Maturity Level Tag. 9
Figure 4 - Deprecated Tag. 9
Figure 5 - Storage Library-centric Instance Diagram . 27
Figure 6 - MediaAccessDevice-centric Instance Diagram . 28
Figure 7 - ChangerDevice-centric Instance Diagram. 28
Figure 8 - Physical View Instance Diagram . 29
Figure 9 - StorageMediaLocation Instance Diagram . 30
Figure 10 - Instance Diagram . 57
Figure 11 - Storage Library Capacity Instance Diagram. 63
Figure 12 - Tape Libraries with Magazines in LimitedAccessPorts. 67
Figure 13 - Tape Libraries with no Magazines in LimitedAccessPorts. 68
© ISO/IEC 2021 – All rights reserved

© ISO/IEC 2021 – All rights reserved

LIST OF TABLES
Table 1 - Supported Profiles for Storage Library .25
Table 2 - CIM Elements for Storage Library .42
Table 3 - SMI Referenced Properties/Methods for CIM_ChangerDevice.48
Table 4 - SMI Referenced Properties/Methods for CIM_Chassis.49
Table 5 - SMI Referenced Properties/Methods for CIM_ComputerSystem.50
Table 6 - SMI Referenced Properties/Methods for CIM_ComputerSystemPackage.50
Table 7 - SMI Referenced Properties/Methods for CIM_ElementCapabilities.50
Table 8 - SMI Referenced Properties/Methods for CIM_ElementSoftwareIdentity.51
Table 9 - SMI Referenced Properties/Methods for CIM_MediaAccessDevice .51
Table 10 - SMI Referenced Properties/Methods for CIM_PackagedComponent .52
Table 11 - SMI Referenced Properties/Methods for CIM_PhysicalMedia .52
Table 12 - SMI Referenced Properties/Methods for CIM_PhysicalMediaInLocation.52
Table 13 - SMI Referenced Properties/Methods for CIM_ProtocolControllerForUnit .53
Table 14 - SMI Referenced Properties/Methods for CIM_Realizes.53
Table 15 - SMI Referenced Properties/Methods for CIM_SCSIProtocolController .53
Table 16 - SMI Referenced Properties/Methods for CIM_SoftwareIdentity.54
Table 17 - SMI Referenced Properties/Methods for CIM_StorageLibraryCapabilities .55
Table 18 - SMI Referenced Properties/Methods for CIM_StorageMediaLocation.55
Table 19 - SMI Referenced Properties/Methods for CIM_SystemDevice (System to Changer Device) .56
Table 20 - SMI Referenced Properties/Methods for CIM_SystemDevice (System to MediaAccessDevice).56
Table 21 - SMI Referenced Properties/Methods for CIM_SystemDevice (System to SCSIProtocolController) .56
Table 22 - CIM Elements for Storage Library Element Counting.61
Table 23 - SMI Referenced Properties/Methods for CIM_ConfigurationReportingService.61
Table 24 - SMI Referenced Properties/Methods for CIM_HostedService .62
Table 25 - CIM Elements for Storage Library Capacity .64
Table 26 - SMI Referenced Properties/Methods for CIM_ConfigurationCapacity .64
Table 27 - SMI Referenced Properties/Methods for CIM_ElementCapacity .65
Table 28 - CIM Elements for Storage Library Limited Access Port Elements .68
Table 29 - SMI Referenced Properties/Methods for CIM_Container .69
Table 30 - SMI Referenced Properties/Methods for CIM_LimitedAccessPort.70
Table 31 - SMI Referenced Properties/Methods for CIM_Magazine.70
Table 32 - SMI Referenced Properties/Methods for CIM_Realizes.71
Table 33 - SMI Referenced Properties/Methods for CIM_SystemDevice.71
© ISO/IEC 2021 – All rights reserved

© ISO/IEC 2021 – All rights reserved

FOREWORD
Storage Library Profile and related component profiles defined in this part provide a standard CIM
interface to monitor and control various aspects of removable media libraries including tape libraries.
Once a library supports this specification, any SMI-S client based on this standard can discover a tape
library, determine its capacity, perform inventory, monitor status, move tapes and perform other
configuration and control operations. This part also standardizes library specific life-cycle and alert
indications that are delivered to a client asynchronously, once a client subscribes to these indications.
This part covers Part 8 (Media Libraries) of the SMI-S standard listed below. While Part 1 describes
SMI-S concepts and terms, some of the profiles referenced in the Storage Library profile are specified in
Part 3 Common Profiles book.
Parts of this Standard
This standard is subdivided in the following parts:
• Storage Management Technical Specification, Part 1 Overview, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 2 Common Architecture, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 3 Common Profiles, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 4 Block Devices, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 5 Filesystems, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 6 Fabric, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 7 Host Elements, 1.8.0 Rev 4
• Storage Management Technical Specification, Part 8 Media Libraries, 1.8.0 Rev 4
SNIA Web Site
Current SNIA practice is to make updates and other information available through their web site at
http://www.snia.org
SNIA Address
Requests for interpretation, suggestions for improvement and addenda, or defect reports are welcome. They
should be sent via the SNIA Feedback Portal at http://www.snia.org/feedback/ or by mail to the Storage Networking
Industry Association, 4360 ArrowsWest Drive, Colorado Springs, Colorado 80907, U.S.A.
© ISO/IEC 2021 – All rights reserved

© ISO/IEC 2021 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 24775-8:2021(E)
1 1 Scope
2 This version of the specification models various details of the following objects of the media library for
3 monitoring.
4 • Library
5 • Drives
6 • Changer Devices
7 • Slots
8 • IO Slots
9 • SCSI Interfaces and SCSI and FC Target Ports
10 • Physical Tapes
11 • Physical Package
12 • Magazines
13 In general, a CIM client can monitor the health and status of the above objects as well as get alert, status
14 change and lifecycle CIM indications. In addition, a client can control the movement of media in a library
15 using this specification.
© ISO/IEC 2021 – All rights reserved

© ISO/IEC 2021 – All rights reserved

1 2 Normative References
2 2.1 General
3 The following referenced documents are indispensable for the application of this document. For dated
4 references, only the edition cited applies. For undated references, the latest edition of the referenced
5 document (including any amendments) applies.
6 2.2 Approved references
7 DMTF DSP1054 v1.2.2, Indications Profile
http://www.dmtf.org/sites/default/files/standards/documents/DSP1054_1.2.2.pdf
9 ISO/IEC 14776-452, SCSI Primary Commands - 3 (SPC-3) [ANSI INCITS.351-2005]
10 2.3 References under development
11 Storage Management Technical Specification, Part 2 Common Architecture, 1.8.0 Rev 4
12 Storage Management Technical Specification, Part 3 Common Profiles, 1.8.0 Rev 4
13 Storage Management Technical Specification, Part 4 Block Devices, 1.8.0 Rev 4
© ISO/IEC 2021 – All rights reserved

© ISO/IEC 2021 – All rights reserved

1 3 Terms, Definitions, Symbols, Abbreviations, and Conventions
2 3.1 General
3 For the purposes of this document, the definitions, symbols, abbreviations, and conventions given in
4 Storage Management Technical Specification, Part 2 Common Architecture, 1.8.0 Rev 4 and the following apply.
5 3.2 Terms and Definitions
3.2.1
changer device
the robotic arm and control logic within a storage media library that moves media from one location to
another
3.2.2
media access device
a device that performs read and write operations on media
Note 1 to entry: In tape libraries, it is the tape drive.
3.2.3
storage media location
one of various locations within a media library where the physical media can be placed
Note 1 to entry: These include the changer devices, the media access devices, physical slots or magazines, and I/O slots.
3.2.4
storage media library
a library in which a large number of removable media can be stored and retrieved
Note 1 to entry: A library also contains a limited number of media access devices for reading and writing to the media.
Note 2 to entry: A changer device within the library moves the media between a stored location and drive or between two locations.
Note 3 to entry: The drives, changers and the library are controlled by a host typically via the SCSI and/or FC ports, but other types
of ports are possible.
Note 4 to entry: A storage media library typically is a tape library.
3.2.5
limited access port
an operator-accessible window of a storage media library through which physical media is fed into the
library or physical media can be retrieved out of a library
Note 1 to entry: A limited access port is also known as an I/O port, import export port, mailslot, etc.
28 3.2.6
library capacity (storage library capacity)
the capacity of a storage media library, measured in terms of the number of physical media it can hold
3.2.7
magazine
a container that holds multiple physical media
Note 1 to entry: Some storage media libraries have magazines that fit into the physical slot instead of single media.
© ISO/IEC 2021 – All rights reserved

© ISO/IEC 2021 – All rights reserved

STABLE
1 4 Storage Library Profile
2 4.1 Synopsis
3 Profile Name: Storage Library (Autonomous Profile)
Version: 1.7.0
Organization: SNIA
Central Class: CIM_ComputerSystem
Scoping Class: ComputerSystem
Supported Profiles: Table 1 describes the supported profiles for Storage Library.
Table 1 - Supported Profiles for Storage Library
Profile Name Organization Version Requirement Description
Access Points SNIA 1.3.0 Optional
Location SNIA 1.4.0 Optional
Software SNIA 1.4.0 Optional
Storage Library Limited Access Port SNIA 1.2.0 Optional
Elements
Storage Library Capacity SNIA 1.1.0 Optional Experimental.
Storage Library Element Counting SNIA 1.1.0 Optional Experimental.
Physical Package SNIA 1.5.0 Mandatory
Launch In Context DMTF 1.0.0 Optional Experimental. See DSP1102, version 1.0.0
Indications DMTF 1.2.2 Mandatory See DSP1054, version 1.2.2
FC Target Ports SNIA 1.7.0 Support for at
23 least one is
SAS Target Ports SNIA 1.7.0
mandatory.
iSCSI Target Ports SNIA 1.8.0
4.2 Description
4.2.1 Profile Goals
The schema for a storage library provides the classes and associations necessary to represent various
forms of removable media libraries. This profile defines the subset of classes that supply the necessary
information for robotic storage libraries.
This profile further describes how the classes are to be used to satisfy various use cases and offers
suggestions to agent implementers and client application developers.
The relevant objects for a storage library should be instantiated in the name space of the provider (or
agent) for a storage library resource. Whenever an instance of a class for a resource may exist in multiple
© ISO/IEC 2021 – All rights reserved

name spaces a durable name is defined to aid clients in correlating the objects across name spaces. For
storage libraries, durable names are defined for the following resources:
• ChangerDevice
• ComputerSystem
• MediaAccessDevice
The durable names are defined in 4.2.8 "Durable Names and Correlatable IDs of the Profile". All other
objects do not require durable names and have instances within a single name space.
4.2.2 Instance Diagrams
The following instance diagrams represent five related views of the Storage Library Profile:
a) System Level
b) MediaAccessDevice and its physical and logical relationships
c) ChangerDevice and its connections to SoftwareIdentity, ProtocolController, and
StorageMediaLocation
d) StorageMediaLocation and its relationship to PhysicalMedia and other physical classes
e) StorageMediaLocation and its required Realizes relationships.
4.2.3 System Level View
Figure 7 shows the required components for a ComputerSystem. Note that LogicalDevice subclasses
shall be associated with ComputerSystem via SystemDevice.
NOTE Classes using a red outline and associations using a dotted outline represent optional components that have been included
in the diagram as an aid to understanding.
© ISO/IEC 2021 – All rights reserved

StorageLibraryCapabilities
Product
RemoteServiceAccessPoint
ProductPhysicalComponent
Element
Capabilities
HostedAccessPoint
SoftwareIdentity
Chassis
SAPAvailable
ForElement
ComputerSystem
InstalledSoftwareIdentity ComputerSystemPackage
(representing a
Storage Library) SystemDevice
SystemDevice
SCSIProtocolController
ChangerDevice
SystemDevice
SystemDevice
ProtocolController
ForUnit
SystemDevice
ProtocolControllerForUnit
MediaAccessDevice
LogicalPort
LimitedAccessPort
TapeDrive
FCPort
Figure 7 - Storage Library-centric Instance Diagram
EXPERIMENTAL
The capabilities of the Storage Library implementation are identified in an instance of
CIM_StorageLibraryCapabilities, which is associated to the top level Storage Library ComputerSystem via
ElementCapabilities. This includes information on the capacity optimization techniques, views,
capabilities and timings supported by the Storage Library implementation.
EXPERIMENTAL
4.2.4 MediaAccessDevice-centric View
Figure 8 shows the required classes related to MediaAccessDevice. Though not shown in this figure, both
MediaAccessDevice and ProtocolController are connected to a ComputerSystem instance through the
SystemDevice association. In some libraries, notably small autoloaders, external hosts access a library’s
ChangerDevice through the ProtocolController of a MediaAccessDevice. For such libraries, an additional
ProtocolControllerForUnit association should be instantiated between the MediaAccessDevice’s
ProtocolController and the affected ChangerDevice. ProtocolControllerForUnit is a many-to-many association,
© ISO/IEC 2021 – All rights reserved

51 so a single ProtocolController can be connected to multiple LogicalDevices if this accurately represents a
52 library’s configuration.
ComputerSystem
System
Device
SCSIProtocolController PhysicalPackage
System
Device
ProtocolController
MediaAccessDevice
Realizes
ForUnit
ElementSoftwareIdentity Realizes
SoftwareIdentity TapeDrive StorageMediaLocation
Figure 8 - MediaAccessDevice-centric Instance Diagram
4.2.5 ChangerDevice-centric View
Figure 9 shows the required classes related to ChangerDevice.
ComputerSystem
SystemDevice
PhysicalPackage
SCSIProtocol
...