SMI Tutorial > SMI-S 1.1.0 Overview > How to Read SMI-S 1.1.0 > How to Read a Profile

Back

How to Read a Profile

Next

Much of the SMI-S 1.1.0 is devoted to describing each Profile and Subprofile in sufficient detail to allow full and proper implementation by a developer. Their descriptions use the same pattern, which consists of

  • General Description
  • Instance Diagrams
  • List of supported Subprofiles
  • List of incorporated Packages
  • Interpretation of the HealthState and OperationalStatus properties
  • Description of the defined Recipes
  • CIM Server Requirements
  • List of mandatory and optional CIM Classes that must be implemented
  • List of mandatory and optional Indication Filters that must be supported
  • For each CIM Class, the list of mandatory and optional Properties and Extrinsic Methods
  • The standards specifications dependencies

The General Description describes how the CIM elements of the Profile are used. In particular, it explains the mapping of the technology components managed by the Profile to the CIM Classes and Properties in the Profile. For example, the Fabric Profile includes a table that maps the various Port types (i.e., N-port, E-port, etc) to the RequestedType property in the FCPortSetting class.

To show CIM elements in diagram form, the SMI-S 1.1.0 uses a variation of the Unified Modeling Language™ (UML) standard specification from the Object Management Group (OMG). The General Description often includes Instance UML diagrams that show the important CIM elements that are used by the Profile.

A Profile can identify Subprofiles that represent optional functionality that a vendor can choose to implement to enhance the Profile capabilities. If a Profile supports other Subprofiles, they are listed in a table. For example, the following table shows that the Profile recognizes the Access Points, Disk Drive Lite, Location and Software Subprofiles. All are optional Subprofile. All are version 1.1.0

 

Registered Subprofile Name

Mandatory

Version

Access Points No 1.1.0
Disk Drive Lite No 1.1.0
Location No 1.1.0
Software No 1.1.0

If the Profile includes CIM elements that contain the HealthState and OperationalStatus properties, then a table is shown that defines how to interpret their possible values. For example,

 

Operational Status

Possible Subsidiary Operational Status

Description

OK The system has good status
Degraded   The system will probably fail sometime soon
Error Non-recoverable error A severe error has occurred. Operator intervention is unlikely to fix it
Stopping The system is shutting down

If the Profile requires that some Extrinsic Methods be supported, then the specification explains what each Method accomplishes. The Profile shows the Method signature and explains how each Method argument is used.

If a Profile supports active management, then the specification also describes the management tasks that can be performed via Intrinsic Methods such as createInstance or deleteInstance. For example, the Fabric Profile explains that the management task of Zone deletion is accomplished by performing a deleteInstance operation.

A Profile can define Recipes that a Client may use to perform a particular management task on the elements managed by the Profile. In the SMI-S 1.1.0, the Recipe name is followed by the descriptive comments and Perl-like expressions that comprise the Recipe. For example, the Fabric Profile lists the Recipes for the following management tasks:

  • Discover The Fabric Topology
  • HBA to switch paths
  • Determine logical path from Switch to Storage Arrays
  • Determine the active Zone Set in a SAN

Next, the Profile shows a table listing the CIM Server functional requirements for the Profile. Examination of this table allows easy determination of two important Profile characteristics. If BasicWrite has a value of No, then the Profile is Read-Only meaning that active management and use of Extrinsic Methods is not allowed. If Indications has a value of No, then a Client cannot ask to be notified when a particular event occurs within the context of this Profile.

The Profile shows a summary table listing the mandatory CIM Classes that must be implemented for the Profile. Optional CIM Classes that a vendor can choose to implement to provide additional capability are also identified. For example, the following table shows that the Profile defines two classes that must be implemented, CIM_ComputerSystem and CIM_FileShare. The Profile also defines one option class, CIM_StorageExtent, that a vendor can choose to implement.

 

Element Name

Description

Mandatory Classes

CIM_ComputerSystem (pg. 863) This declares that at least one computer system must pre-exist
CIM_FileShare (pg. 886) Represents the sharing characteristics of a particular file element

Optional Classes

CIM_StorageExtent (pg. 890) Represents the LUNs that are imported

The Profile shows a table listing the mandatory Indication Filters that must be supported. Optional Indication Filters that a vendor can choose to support to provide additional capability are also listed. For example, the following table shows that the Profile allows a Client to be notified when a new array comes online.

 

Element Name

Description

Mandatory Indications

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_ComputerSystem Addition of a new array instance

After the summary tables, the Profile shows a table for each identified CIM Class. Each table lists the mandatory Properties in the CIM Class that must be implemented. Optional Properties that a vendor can choose to support to provide additional capability are also listed. For some Properties, the Description field show a required value or set of values for that Property. For example, the following table shows that the Profile allows a Client to retrieve information about the FC Port. An implementation must ensure that the SystemName, OperationalStatus and LinkTechnology properties in the CIM_FCPort class have values. The SystemName is a string property. The OperationalStatus is an array of unsigned 16-bit integers.The LinkTechnology property is an integer whose value will be the integer value that represents "FC". The implementation can optionally choose to populate the ElementName string property.

SMI Referenced Properties/Methods for CIM_FCPort

Property

Flags

Type

Description and Notes

Mandatory Properties/Methods

SystemName   string The scoping System's name
OperationalStatus   uint16[] One of the defined values shall be present
LinkTechnology   uint16 "FC"

Optional Properties/Methods

ElementName   string Port symbolic name

Finally, the Profile shows a table listing the standards upon which it depends. For example, the following table shows that the Profile depends upon  the DMTF CIM Infrastructure Specification version 2.3.0, the DMTF CIM Operations over HTTP specification version 1.2.0 and the DMTF CIM Schema version 2.11.0.

 

Specification

Revision

Organization

CIM Infrastructure Specification

2.3.0

DMTF

CIM Operations over HTTP 1.2.0 DMTF
CIM Schema 2.11.0 DMTF

 

Back Next