| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 36450.3-2024 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Information technology - Storage management - Part 3: Common profiles
| Valid |
GB/T 36450.3-2024
|
PDF similar to GB/T 36450.3-2024
Basic data | Standard ID | GB/T 36450.3-2024 (GB/T36450.3-2024) | | Description (Translated English) | Information technology - Storage management - Part 3: Common profiles | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.200 | | Word Count Estimation | 314,327 | | Date of Issue | 2024-04-25 | | Date of Implementation | 2024-11-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 36450.3-2024: Information technology - Storage management - Part 3: Common profiles---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
ICS 35:200
CCSL77
National Standards of People's Republic of China
Information Technology Storage Management
Part 3: General profiles
(ISO /IEC 24775-3:2021, IDT)
Released on 2024-04-25
2024-11-01 Implementation
State Administration for Market Regulation
The National Standardization Administration issued
Table of Contents
Preface IX
Introduction Ⅹ
1 Scope 1
2 Normative references 1
2:1 Adopted references 1
2:2 DMTF Reference Document (Final) 1
2:3 References in development 2
3 Terms and Definitions 2
3:1 Overview 2
3:2 Terminology 2
4 Contour Guide 2
4:1 Overview 2
4:2 Description 3
4:3 Outline format description 3
5 Generic Target Port Outline 6
5:1 Overview 6
5:2 Description 6
5:3 Implementation 6
5:4 Contour Method 8
5:5 Use Case 8
5:6 CIM Elements 8
6 FC target port profile 12
6:1 Overview 12
6:2 Description 12
6:3 Implementation 12
6:4 Persistent Names and Correlation IDs of Profiles 12
6:5 Health and fault management considerations 13
6:6 Supported Profiles and Packages 13
6:7 External methods of contours 13
6:8 Client Notes and Methods 13
6:9 CIM Elements 13
7 FCoE Target Port Profile 17
7:1 Overview 17
7:2 Description 17
7:3 Implementation 17
7:4 Persistent Names and Correlation IDs of Profiles 18
7:5 Method 19
7:6 Use Case 19
7:7 CIM Elements 19
8 iSCSI target port profile 24
8:1 Overview 24
8:2 Description 24
8:3 Implementation 24
8:4 Health and Fault Management Considerations 27
8:5 Contour Methods 27
8:6 Client Notes and Methods 32
8:7 CIM Elements 32
9 Serial SCSI Target Port Profile 54
9:1 Overview 54
9:2 Description 54
9:3 Health and Fault Management Considerations 55
9:4 Method 55
9:5 Client Notes and Methods 55
9:6 CIM Elements 55
10 Serial ATA Target Port Profile 60
11 SB Target Port Profile 61
11:1 Overview 61
11:2 Description 61
11:3 Implementation 61
11:4 Health and Fault Management Considerations 62
11:5 Cascading considerations 62
11:6 Contour Methods 62
11:7 Client Notes and Methods 63
11:8 CIM Elements 63
12 Directly connected to the profile 67
12:1 Overview 67
12:2 Description 67
12:3 Health and Fault Management Considerations 68
12:4 External Methods 68
12:5 Use Case 68
12:6 CIM Elements 68
13 Generic Initiator Port Profile 71
13:1 Overview 71
13:2 Description 71
13:3 Implementation 71
13:4 Methods 75
13:5 Use Cases 75
13:6 CIM Elements 76
14 Parallel SCSI (SPI) Initiator Port Profile 82
14:1 Overview 82
14:2 Description 82
14:3 Implementation 82
14:4 Method 83
14:5 Use Cases and Methods 83
14:6 CIM Elements 83
15 iSCSI Initiator Port Profile 90
15:1 Overview 90
15:2 Description 90
15:3 Achieving 90
15:4 Methods 91
15:5 Use Cases and Methods 92
15:6 CIM Elements 92
16 FC Initiator Port Profile 98
16:1 Overview 98
16:2 Description 98
16:3 Implementing 98
16:4 Method 99
16:5 Use Cases and Methods 100
16:6 CIM Elements 100
17 SAS Initiator Port Profile 109
17:1 Overview 109
17:2 Description 109
17:3 Health and Fault Management Considerations 109
17:4 Contour Methods 110
17:5 Client Notes and Methods 110
17:6 CIM Elements 110
18 ATA Initiator Port Profile 120
19 SB Starter Port Profile 121
19:1 Overview 121
19:2 Description 121
19:3 Implementation 121
19:4 Methods 122
19:5 Client Notes and Methods 122
19:6 CIM Elements 122
20 FCoE Initiator Port Profile 130
20:1 Overview 130
20:2 Description 130
20:3 Implementation 130
20:4 Methods 132
20:5 Use Cases and Methods 133
20:6 CIM Elements 133
21 Access Point Profile 145
21:1 Overview 145
21:2 Description 145
21:3 Health and Fault Management Considerations 146
21:4 Cascading considerations 146
21:5 Contour Methods 146
21:6 Client Notes and Methods 146
21:7 CIM Elements 147
22 Health Pack Outline 149
22:1 Overview 149
22:2 Description 149
22:3 Report 149
22:4 Health and Fault Management Considerations 152
22:5 Cascading considerations 153
22:6 Use Cases 153
22:7 CIM Elements 153
23 Mission Control Profile 155
23:1 Overview 155
23:2 Overview 155
23:3 Health and Fault Management Considerations 158
23:4 Cascading considerations 158
23:5 Contour Methods 158
23:6 Client Notes and Methods 159
23:7 Registered Name and Version 160
23:8 CIM Elements 160
24 Position Profile 165
24:1 Overview 165
24:2 Description 165
24:3 Example Figure 165
24:4 Health and Fault Management Considerations 165
24:5 Cascading considerations 166
24:6 Contour Methods 166
24:7 Use Cases 166
24:8 CIM Elements 166
25 Multicomputer System Outline 168
25:1 Overview 168
25:2 Description 168
25:3 Health and Fault Management Considerations 172
25:4 Cascading considerations 172
25:5 Contour Methods 172
25:6 Use Cases 172
25:7 CIM Elements 172
26 Physical Package Outline 176
26:1 Overview 176
26:2 Description 176
26:3 Health and Fault Management Considerations 178
26:4 Cascading considerations 178
26:5 Contour Methods 178
26:6 Use Cases 178
26:7 CIM Elements 179
27 Power Outline 185
27:1 Overview 185
27:2 Description 185
27:3 Implementation 185
27:4 Methods 185
27:5 Use Cases 185
27:6 CIM Elements 185
28 Fan Profile 191
28:1 Overview 191
28:2 Description 191
28:3 Implementation 191
28:4 Methods 191
28:5 Use Cases 191
28:6 CIM Elements 192
29 Sensor Profile:199
29:1 Overview:199
29:2 Description:199
29:3 Implementation:199
29:4 Methods:199
29:5 Use Cases:199
29:6 CIM Elements:199
30 Basic Server Profile 206
30:1 Overview 206
30:2 Description 206
30:3 Implementation 207
30:4 Methods 207
30:5 Use Cases 207
30:6 CIM Elements 207
31 Media Access Device Profile 212
31:1 Overview 212
31:2 Description 212
31:3 Implementation 213
31:4 Methods 214
31:5 Use Cases 214
31:6 CIM Elements 214
32 Storage Chassis Outline 219
32:1 Overview 219
32:2 Description 219
32:3 Implementation 221
32:4 Methods 223
32:5 Use Cases 224
32:6 CIM Elements 224
33 Software Profile 236
33:1 Overview 236
33:2 Description 236
33:3 Health and Fault Management Considerations 236
33:4 Cascading considerations 237
33:5 Contour Methods 237
33:6 Use Cases 237
33:7 CIM Elements 237
34 Software Inventory Profile 239
34:1 Overview 239
34:2 Description 239
34:3 Implementation 240
34:4 Methods 240
34:5 Use Cases 240
34:6 CIM Elements 240
35 Server Profile 246
35:1 Overview 246
35:2 Description 246
35:3 Health and Fault Management 248
35:4 Cascading considerations 248
35:5 CIM Elements 248
36 Profile Registration Profile 253
36:1 Overview 253
36:2 Description 253
36:3 Implementation 253
36:4 Method 256
36:5 Use Case 256
36:6 CIM Elements 256
37 Indicator outline 262
38 Object Manager Adapter Profile 263
39 Proxy Server System Administration Profile 264
40 Device Certificate Profile 265
40:1 Overview 265
40:2 Description 265
40:3 Health and Fault Management Considerations 265
40:4 Cascading considerations 265
40:5 External methods of contours 266
40:6 Use Cases 266
40:7 CIM Elements 266
41 Operation Power Profile 268
41:1 Overview 268
41:2 Description 268
41:3 Implementation 268
41:4 Contour Methods 275
41:5 Use Cases 279
41:6 Client Notes and Methods 279
41:7 CIM Elements 279
42 Indicator outline 293
43 WBEM Server Profile 294
Appendix A (Informative) SMI-S Information Model 295
Appendix B (Informative) Cross-profile considerations 296
B:1 Overview 296
B:2 HBA Model 296
B:3 Switch Model 296
B:4 Array Model 297
B:5 Storage Virtualization Model 298
B:6 Fabric Topology (HBA, Switch, Array) 299
References 300
Foreword
This document is in accordance with the provisions of GB/T 1:1-2020 "Guidelines for standardization work Part 1: Structure and drafting rules for standardization documents"
Drafting:
This document is Part 3 of GB/T 36450 "Information Technology Storage Management": GB/T 36450 has been published in the following parts:
--- Part 1: Overview;
--- Part 2: General architecture;
--- Part 3: General profile;
--- Part 5: File system;
--- Part 6: Switching structure;
--- Part 7: Host elements;
--- Part 8: Media Library:
This document is equivalent to ISO /IEC 24775-3:2021 "Information technology storage management Part 3: Common profile":
The following minimal editorial changes were made to this document:
--- Corrected the article numbers of 32:6:18~32:6:24 in the international standard;
--- Corrected the numbering of the drawings in the international standards:
Please note that some of the contents of this document may involve patents: The issuing organization of this document does not assume the responsibility for identifying patents:
This document was proposed and coordinated by the National Technical Committee for Information Technology Standardization (SAC/TC28):
This document was drafted by: Huazhong University of Science and Technology, China Electronics Technology Standardization Institute, Shenzhen CESI Information Technology Co:, Ltd:, Northwestern Polytechnical University
University of Commerce, Dell EMC Information Technology (Beijing) Co:, Ltd:, Jiangsu CESI Technology Development Co:, Ltd:, Sichuan Changhong Jiahua Information Products Co:, Ltd:
Co:, Ltd:, China University of Geosciences (Wuhan), Huawei Technologies Co:, Ltd:, Hangzhou Hikvision Digital Technology Co:, Ltd:, Inspur Electronics
Information Industry Co:, Ltd:, Shenzhen Urban Transportation Planning and Design Research Center Co:, Ltd:, Zhejiang Bangsheng Technology Co:, Ltd:
China Mobile Information Technology Co:, Ltd:, Terminus Technology Group Co:, Ltd:, Beijing Xiaomi Mobile Software Co:, Ltd:, Chengdu University of Information Engineering
Shenzhen Baoteng Interconnect Technology Co:, Ltd:, BlueCore Storage Technology (Ganzhou) Co:, Ltd:, Hubei Huazhong Electric Power Technology Development Co:, Ltd:
Co:, Ltd:, Shenzhen Jinding Weishi Technology Development Co:, Ltd:
The main drafters of this document are: Feng Dan, Yang Hong, Zhou Hai, Sun Wei, Zhang Xiao, Zhuo Lan, Guo Xiong, Tang Haiying, He Xia, Zhang Chi, Deng Ze, Zhao Lili,
Lei Gen, Wang Weichun, Wang Fang, Chen Jianxi, Hu Renchong, Zhao Xiangyang, Liu Tao, Li Ying, Feng Yi, Yang Yu, Zhou Juejia, Wu Xi, Xu Guanglei, Liu Yang,
Shi Yulu, Yang Jing, Zheng Yuanyuan, Zhang Xiaochun, Zhang Guiyong, Liu Kang, Wang Chengning, Bai Xinlu, Wu Bing, Lin Tao, Wang Xiaoyan, Zhang Xiaojing, Tang Yin, Yang Tianyuan,
Zhuang, Xiaopeng, Li, Yilun, Huang, Wenjie, and Xu, Zhihui:
Introduction
0:1 Description of the text structure of GB/T 36450
GB/T 36450 "Information Technology Storage Management" is a recommended standard to guide the standardization of storage management in my country:
The quasi-management interface solves the interoperability of multi-vendor products and the management issues of cross-regional, multi-functional distributed storage systems:
GB/T 36450 is compiled based on ISO /IEC 24775 and consists of eight parts:
--- Part 1: Overview: The purpose is to provide a high-level introduction to key concepts and to understand the details of GB/T 36450:
important foundation:
--- Part 2: General architecture: The purpose is to establish a general transmission model to exchange management information between management system components:
The general transmission model is introduced, and the design rules of the general transmission model are given, as well as the roles and responsibilities of each component using the general transmission model:
--- Part 3: Generic Profile: The purpose is to establish a unified solution across multiple autonomous management profiles for storage management systems
Other profiles are supported:
--- Part 4: Block devices: The purpose is to establish a configuration interface for storage management systems that is secure, scalable, and interoperable:
The interface is designed through object-oriented, XML-based and information-transfer protocols to support management devices and subsystems in different environments:
System requirements:
--- Part 5: File system: The purpose is to establish the autonomous management profile of programs and equipment, and the support and
Access to core functionality requirements:
--- Part 6: Switching structure: The purpose is to establish the autonomous management profile of the programs and devices that provide support for storage networking:
--- Part 7: Host elements: The purpose is to establish autonomous management profiles based on host storage devices, components and abstract profiles
Require:
--- Part 8: Media Library: The purpose is to establish the modeling details requirements for monitoring media library objects:
0:2 Typographical Conventions
In addition to informative and normative content, this document contains guidance on emerging materials that have undergone rigorous design review:
However, implementation in commercial products is limited: The purpose of typographical conventions is to provide appropriate
The implementer should make a further decision as to whether to include the material in the
Adoption and deployment of various parts of this document in commercial products:
This document is structured to provide both formal requirements and guidance for the implementation and deployment life cycle of GB/T 36450 and its new products:
In summary, all the contents of this document will show a mature and stable design, which will be tested by a large number of implementations to ensure
backwards compatible with the same support, and only rely on content material that has reached a similar maturity level:
For all other content, it is assumed that they meet these requirements and are called "complete":
In any implementation of a standard, there is much that does not reach this level of “completion”, so this document defines three levels of implementation maturity:
Sub-levels, which identify important aspects of the increasing maturity and stability of the technical content: Each sub-maturity level is actually
Each sub-maturity level is defined by its degree of experience, stability, and dependency on other emerging standards:
The content of one maturity model level is clearly distinguished from that of another level by means of a signatory agreement:
Experimental Maturity Level: This document contains only technical content for which the initial architecture has been completed and has passed design review:
Some of the technical content has been designed and reviewed, but lacks implementation experience and the maturity gained from implementation experience:
The purpose of this document is to gain more extensive review and implementation experience: This material will be marked as "experimental":
The content of the "experimental" profile may be modified as products are implemented:
The experimental material will be updated as it is implemented:
Figure 1 is an example of typographical conventions for experimental content:
Figure 1 Experimental maturity level label
Implementation maturity level: Profiles that have completed preliminary implementations are classified as "implemented": This means that at least two different vendors have implemented
At this maturity level, the underlying architecture and modeling process are stable and future versions of the
This change is limited to correcting defects found in more implementation experience: If such material becomes outdated in the future, it will be removed from subsequent implementation versions:
Before deletion, the material is discarded when minor changes are made to this document: Figure 2 is an example of the typographical conventions of the implemented content:
Figure 2 Implementation maturity level labels
Stable maturity level: Once content at the Implemented maturity level has gained more implementation experience, it can be marked as Stable:
The material at this maturity level has been implemented by three different vendors, including a provider and a customer:
If material that has reached this maturity level becomes obsolete, it may be discarded when making minor revisions to this document:
When making minor changes to produce the next version, backward compatibility with profiles that have reached this maturity level is guaranteed:
The outline of the Stable maturity level does not depend on any content in the Experimental maturity level: Figure 3 is a typographical outline of the Stable content:
Set example:
Figure 3 Stable maturity level label
Completed maturity level: Content that reaches the highest maturity level is called "completed": In addition to meeting the requirements of the stable level of maturity
Otherwise, content at the Done level of maturity depends only on material that has reached Done level or its refinements:
SNIA controls material that is not subject to its maturity definition, SNIA will evaluate the external content to ensure that it has achieved comparable maturity:
If material that has reached this maturity level becomes outdated, significant revisions may be made to this document:
Profiles reaching this maturity level guarantee backward compatibility with each minor revision of this document:
All contents of this document meet this maturity level: Therefore, there is no special requirement for this maturity level as there is for other maturity sub-levels:
For content in this document that is not marked using one of the typographical conventions specified for the sub-maturity level, it is recommended to assume that
It has reached completion level maturity:
Deprecated Material: Experimental material that may be deprecated in subsequent revisions of this document is not included: Sections marked "deprecated" contain
The material is outdated and is not recommended for use in new development work: Existing and new implementations may still use this material, but should be updated as soon as possible:
Adopt new approaches: How long newly deprecated material stays in the standard depends on its maturity level:
Deprecated material is reserved for the next major revision of this document, while "stable" and "finished" material is reserved for the next major revision of this document:
Providers are required to implement deprecated material as long as it appears in this document to ensure backward compatibility: Clients may depend on deprecated material, but are encouraged to
Encourage the use of non-deprecated alternatives where possible:
The deprecated clauses are arranged by citing the previous version, and the deprecated clauses are included as normative materials in the replacement clauses of the current standard:
Figure 4 is an example of typographical conventions for deprecated content:
Figure 4 Deprecation label
Information Technology Storage Management
Part 3: General profiles
1 Scope
This document defines the general outline required by other parts of GB/T 36450: The previous clauses provide background information that helps explain the purpose and overview:
The generic port profiles are grouped together because they serve as transmission-specific variations of the generic model: The port profiles are followed by their
He has a universal outline:
2 Normative references
The contents of the following documents constitute the essential clauses of this document through normative references in this document:
For referenced documents without a date, only the version corresponding to that date applies to this document; for referenced documents without a date, the latest version (including all amendments) applies to
This document:
2:1 Approved References
Storage management-Part 2: Common Architecture)
Note: GB/T 36450:2-2021 Information technology storage management Part 2: General architecture
2:2 DMTF Reference Document (Final)
The DMTF final document is accepted as a standard:
http://www:dmtf:org/sites/default/files/standards/documents/DSP1004_1:0:1:pdf
http://www:dmtf:org/sites/default/files/standards/documents/DSP1009_1:1:1:pdf
http://www:dmtf:org/standards/published_documents/DSP1011_1:0:2:pdf
DMTFDSP1013:2008 Fan Profile (FanProfile1:0:1)
http://www:dmtf:org/standards/published_documents/DSP1015_1:1:0:pdf
http://www:dmtf:org/standards/published_documents/DSP1023_1:0:1:pdf
http://www:dmtf:org/standards/published_documents/DSP1025_1:0:0:pdf
http://www:dmtf:org/sites/default/files/standards/documents/DSP1052_1:0:3:pdf
http://www:dmtf:org/sites/default/files/standards/documents/DSP1054_1:2:2:pdf
|