Reference Guide
Dell OpenManage Client Instrumentation Reference Guide
file:///T|/htdocs/SOFTWARE/smcliins/cli80/EN/refgd/index.htm[10/19/2012 9:56:27 AM]
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
methods in SoftwareInstallationService return a reference to that Job as the Job parameter.
Possible values are:
2 - None supported
3 - Install From Software Identity
4 - Install from ByteStream
5 - Install from URI
SupportedInstallOptions
An enumeration indicating the specific install related optionssupported by this service. Since this is an array, multiple values may be specified.
See the InstallOptions parameter of theSoftwareInstallationService.InstallFromSoftwareIdentity method for the description of these values.
Possible values are:
2 - Defer target/system reset
3 - Force installation
4 - Install
5 - Update
6 - Repair
7 - Reboot
8 - Password
9 - Uninstall
10 - Log
11 - SilentMode
12 - AdministrativeMode
.. - DMTF Reserved
32768..65535 - Vendor Specific
SupportedTargetTypes
An array containing a list of SoftwareIdentity.TargetType properties that this service 'knows' how to install. TargetType is an application specific
string which is invariant across version or name changes of the SoftwareIdentity and so can be used by a client to select Software Identities
compatible with this service.
If the service is generic (for example an OS installer), this array will be empty.
SupportedURISchemes
This property lists the URI schemes supported by the SoftwareInstallationService.
Possible values are:
2 - data
3 - file
4 - ftp
5 - http
6 - https
7 - nfs
8 - tftp
.. - DMTF Reserved
0x8000..0xFFFF - Vendor Specific
DCIM_ConcreteCollection
ElementName
A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity
data, and description information.
Note: The Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not
reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a
Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties.
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 unique name. It can be a copyrighted,
trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID. Or, it could be a
registered ID that is 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 re-used to identify different underlying (real-world) elements. If the above
'preferred' algorithm is not used, the defining entity must ensure that the resulting InstanceID is not re-used as any of the InstanceIDs produced
by this or other providers for the NameSpace of this instance.
DCIM_RedundancySet
ElementName
A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity
data, and description information.
Note: The Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not
reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a
Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties.
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 unique name. It can be a copyrighted,
trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID. Or, it could be a
registered ID that is 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 re-used to identify different underlying (real-world) elements. If the 'preferred'
algorithm is not used, the defining entity must ensure that the resulting InstanceID is not re-used as any of 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'.
MinNumberNeeded
Indicates the smallest number of elements that MUST be operational in order to function. For example, in an N+1 redundancy relationship, the
MinNumberNeeded property is set equal to N. In a 'LimitedSparing' environment, this property is meaningless and SHOULD be set to zero.
RedundancyStatus
Provides information on the state of the RedundancyGroup.
Possible values are:
0 - Unknown
1 - DMTF Reserved
2 - Fully Redundant - Indicates that all of the configured redundancy is still available
3 - Degraded Redundancy - Indicates that some configured elements are degraded, missing or failed but that the number of elements in the set
is still greater than the minimum required ('MinNumberNeeded');
4 - Redundancy Lost - Indicates that sufficient configured elements are missing or failed that no redundancy is available and the next failure
experienced will cause overall failure.
5 - Overall Failure - Indicates that there has been an overall failure of the RedundancySet.
Provides information on the type of redundancy. - N+1 ( - 2) indicates all members are active, are unaware and function independent of one