ISO/IEC 24775-6:2021

INTERNATIONAL ISO/IEC
STANDARD 24775-6
Second edition
2021-03
Information technology — Storage
management —
Part 6:
Fabric
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 6 Fabric,
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-6: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.
— Blades Profile
— Added descriptions for References in CIM_ProductPhysicalComponent.
— Changed the version to 1.7.0.
— Enhanced Zoning and Enhanced Zoning Control Profile (SMI TWG Reviews)
— Fixed the version numbers on the Related Profiles to match what the profiles claim.
— Fabric Profile
— Corrected the Related Profile for FabricVirtualFabrics to be Virtual Fabrics.
— Fixed the version numbers on the Related Profiles to match what the profiles claim.
— Deleted the MemberOfCollections in the CIM Elements for the filter collections that were
deleted.
— Defined the condition for Peer Zoning in CIM_ZoneSettingData ZoneMembershipSettingData to
Zone).
— Fabric Views Profile
— In FCSwitchView changed OperationalStatus to SwitchOperationalStatus and
FCPortEnabledState to PortEnabledState.
— In ConcreteComponentView changed Antecedent and Dependent to GroupComponent and
PartComponent.
— Changed the version of the profile to 1.7.0.
— Changed the Central Class from FCTopologyView to CIM_ViewCapabilities (TSG-SMIS-
SCR00333).
— FCoE Fabric (TSG-SMIS-SCR00331)
— Reworked the profile to be a component profile of the Fabric Profile.
— Removed the classes associated with experimental indications.
— Added a definition of CIM_EthernetPort (which was missing).
— Fixed a number of mifgen warnings.
— FDMI Profile
— Changed the version of the Profile to be 1.8.0, since we expanded the Speed enumerations
— Inter Fabric Routing Profile
— Added a SystemDevice between the IFR Switch and the IFR FCPort.
— Changed the Profile version to 1.7.0.
— Changed the Central Class from ComputerSystem to CIM_ComputerSystem (IFR Switch) (TSG-
SMISSCR00333).
— N Port Virtualizer Profile
— Fixed the version numbers on the Related Profiles to match what the profiles claim.
— Changed the Central Class from FCPort to CIM_FCPort (Fabric NPIV) (TSG-SMIS-SCR00333).
iv © ISO/IEC 2021 – All rights reserved

— Switch Partitioning Profile
— Changed the name of the profile to "Switch Partitioning" to make the spec readable.
— Changed “must” to “shall” in a number of CIM Element tables.
— Changed the Central Class from ComputerSystem to CIM_ComputerSystem (Partitioning) (TSG-
SMISSCR00333).
— Switch Profile
— Fixed the version numbers on the Related Profiles to match what the profiles claim.
— Changed the version of the profile to 1.8.0, due to changes to the enumeration of the Speed
property.
— Removed the Switch Configuration Data profile from Related Profiles table, since it has been
removed from the spec.
— Changed the name of the FabricSwitchPartitioning Profile to Switch Partitioning in the Related
Profiles table.
— Changed the Requirement for CIM_ElementSettingData (FCSwitchSettings to ComputerSystem)
to Mandatory, since FCSwitchSettings and the Switch are Mandatory.
— Virtual Fabrics Profile
— Changed the name of the profile to "Virtual Fabrics" to make the spec readable.
— Zone Control Profile
— Changed the version of the Profile to be 1.8.0, since we added two methods.
— Annex B (Informative) Structure of Fabric Profiles (TSG-SMIS-SCR00331)
— Updated Figure B.1 to show how FCoE Fabrics fits into the structure of Fabric profiles.
— References
— Added DMTF DSP1054 v1.2.2, Indications Profile (and changed to V1.2.2 throughout book).
— Removed SPC-2.
— Moved SPC-3 reference from 2.2 to 2.1.
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.
© ISO/IEC 2021 – All rights reserved v

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 resul
...