Reference Guide
DCIM_BIOSServiceCapabilities
Table 84. BIOSServiceCapabilities
Property Description
InstanceID
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'.
MethodsSupported
This property advertises the methods that are supported by the service .
Possible values are:
• 0 = SetBIOSAttribute
• 1 = RestoreBIOSDefaults
• 2 = SetBIOSAttributeEmbeddedInstance
• 3 = ReadRawBIOSData
• 4 = WriteRawBIOSData
• 5 = SetBIOSAttributes
• 6..65535 = DMTF Reserved
• 65536..4294967295 = Vendor Specified
DCIM_SoftwareInstallationServiceCapabilities
Table 85. SoftwareInstallationServiceCapabilities
Property Description
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely
identifies an instance of this class. 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 that is creating or defining the InstanceID or that is a registered ID assigned
to the business entity by a recognized global authority. (This requirement 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 reused to identify different underlying (real-world)
elements. If the above
preferred algorithm is not used, the defining entity must assure that
the resulting InstanceID is not reused across any InstanceIDs produced by this or other
providers for the NameSpace of this instance. For DMTF-defined instances, the
preferred
algorithm must be used with the <OrgID>set to CIM.
SupportedAsynchronousActions
Enumeration indicating what operations will be executed as asynchronous jobs. If an
operation is included in both this and SupportedSynchronousActions then the underlying
implementation is indicating that it may or may not create a job. If a Job is created, then the
Dell Command | Monitor 10.2.1 classes and properties 211