CIM_iSCSIConfigurationCapabilities class

A subclass of Capabilities that defines the capabilities of a iSCSIConfigurationService.

The following syntax is simplified from Managed Object Format (MOF) code and includes all of the inherited properties.

Syntax

[Abstract, Experimental, Version("2.10.0"), UMLPackagePath("CIM::Network::iSCSI")]
class CIM_iSCSIConfigurationCapabilities : CIM_Capabilities
{
  string  Caption;
  string  Description;
  string  InstanceID;
  string  ElementName;
  boolean iSCSIProtocolEndpointCreationSupported = FALSE;
  boolean IdentifierSelectionSupported = FALSE;
  boolean iSCSINodeCreationSupported = FALSE;
};

Members

The CIM_iSCSIConfigurationCapabilities class has these types of members:

• Properties

Properties

The CIM_iSCSIConfigurationCapabilities class has these properties.

Caption

Data type: string

Access type: Read-only

Qualifiers: MaxLen (64)

The Caption property is a short textual description (one- line string) of the object.

This property is inherited from CIM_ManagedElement.

Description

Data type: string

Access type: Read-only

Contains a textual description of the object.

This property is inherited from CIM_ManagedElement.

ElementName

Data type: string

Access type: Read-only

Qualifiers: Required

The user friendly name for this instance of Capabilities. In addition, the user friendly name can be used as a index property for a search of query. (Note: Name does not have to be unique within a namespace.)

This property is inherited from CIM_Capabilities.

IdentifierSelectionSupported

Data type: boolean

Access type: Read-only

If false, the implementation chooses the Identifier for the iSCSIProtocolEndpoint and the Identifier cannot be supplied as a parameter to CreateiSCSIProtocolEndpoint and MUST be NULL.

InstanceID

Data type: string

Access type: Read-only

Qualifiers: Key

Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following 'preferred' algorithm: <OrgID>:<LocalID> Where <OrgID> and <LocalID> are separated by a colon ':', and where <OrgID> MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness <OrgID> MUST NOT contain a colon (':'). When using this algorithm, the first colon to appear in InstanceID MUST appear between <OrgID> and <LocalID>. <LocalID> is chosen by the business entity and SHOULD not be re-used to identify different underlying (real-world) elements. If the above 'preferred' algorithm is not used, the defining entity MUST assure that the resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance's NameSpace. For DMTF defined instances, the 'preferred' algorithm MUST be used with the <OrgID> set to 'CIM'.

This property is inherited from CIM_Capabilities.

iSCSINodeCreationSupported

Data type: boolean

Access type: Read-only

iSCSI Nodes are modeled by instances of SCSIProtocolController. If true, this property indicates that iSCSI Nodes may be dynamically created and deleted in a NetworkEntity. If false, iSCSI Nodes are pre-existing and statically defined within the Entity.

iSCSIProtocolEndpointCreationSupported

Data type: boolean

Access type: Read-only

iSCSI Ports are modeled by instances of iSCSIProtocolEndpoints. If true, this property indicates that iSCSIProtocolEndpoints may be dynamically created and deleted in a Node. If false, iSCSIProtocolEndpoints are preexisting and statically defined within the Node.

Requirements

See also

CIM_Capabilities