Reference Guide

Property Description
source input parameter. That is, the first position in the array will
have the lowest value for AssignedSequence. The second
position will have the second lowest value, and so on. For
BootSourceSetting instances which are associated with the
BootConfigSetting instance via OrderedComponent and not
present in the input array, the AssignedSequence property on the
OrderedComponent association will be assigned a value of 0.
DCIM_IPAssignmentSettingData
Property Description
AddressOrigin
AddressOrigin identifies the method by which the IP Address, Subnet
Mask, and Gateway were assigned to the IPProtocolEndpoint.
Possible values are:
• 0 = Unknown
• 1 = Other
• 2 = Not Applicable - Indicates that the application of the
IPAssignmentSettingData instance does not affect these
properties.
• 3 = Static - Indicates that values for the properties are
contained in the IPAssignmentSettingData instance.
• 4 = DHCP - Indicates that the values will be assigned via DHCP.
• 5 = BOOTP - Iindicates that the values will be assigned via
BOOTP.
• 6..32767 = DMTF Reserved
• 32768.. = Vendor Reserved
ElementName
The user-friendly name for this instance of SettingData. In addition, the
user-friendly name can be used as an index property for a search or
query.
NOTE: The name does not have to be unique within a namespace.
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
210